The goal with this assignment has been to study the product Spotalike and develop a new version to make the product more attractive. The studying of the product was done with the help of user data, such as how Spotalike is being used, what target audience it has, why it's being used, etc. The new version of Spotalike was planned by making design sketches and prototypes which were created as a first step in order to get a better picture of what the result would be. The new version is not available to the public, but it is fully functional and works locally. The solution that was concluded was to develop a music player which is built on the founding principles of the old Spotalike. The music player is developed with React and is powered by Spotify. Besides the old functions there are also new functions that has been implemented, and the interface has been redesigned. There is currently no new user data available to determine the result of the development, since the new version of Spotalike hasn't been made public yet. / Målet med detta projektarbete har varit att granska produkten Spotalike och utveckla en ny version som gör produkten mer eftertraktad. Problemgranskning har gjorts med analysering av användardata – hur Spotalike används, av vem, varför den används, osv. Den nya versionen av Spotalike planerades med hjälp av designskisser och prototyper som togs fram som första steg för att få en bättre bild av slutresultatet. Den nya versionen är inte tillgänglig publikt, men är fullt funktionell lokalt. Lösningen som togs fram var att skapa en musikspelare som bygger på de grundprinciper gamla Spotalike har. Musikspelaren är bygd med React och använder Spotify i bakgrunden som motor. Utöver de redan befintliga funktionerna så har även nya funktioner tagits fram och gränssnittet har redesignats. Någon ny användarstatistik för att se om lösningen har gynnat bra resultat i form av användarupplevelse finns inte tillgänglig då tjänsten ännu inte har hunnit bli tillgängligt publikt.

In a big organization there are many events organized every day. To know about the events, we typically need to check an events page, rely on flyers or on distributed pamphlets or through word of mouth. To register for an event a user now a days typically does this online which involves inputting user details. At the event, the user either signs a sheet of paper or enters credentials in a web page loaded on a tablet or other electronic device. Typically, this is a time-consuming process with many redundancies like entering user details every time the user wants to register for a new event and re-entering the details at the event. This project designs a system that eliminates these redundancies and improves event management.

<p>Background: In recent research literature, some researchers mean that companies in fast changing markets have to act proactively while others find that companies have to adapt to conditions and to react. This makes it interesting to study how software companies act strategically and also to study to what extent a flexible organisation is required by companies who proact and by those who react. </p><p>Purpose: The purpose of this thesis is the study how different types of software companies act strategically and what this requires of the company in terms of flexibility. </p><p>Delimitation: The study treats only Swedish software companies with more than ten employees. Proceed of the Study: Representatives from four case companies as well as a consultant have been interviewed. As a complement to the case study, a survey has also been conducted where 36 companies have participated. </p><p>Results: Only one of the four case companies can be said to act proactively. Among the survey companies, there are principally young companies, companies with a leading position on the market and companies that experience high growth that act proactively. Companies that work proactively value to a greater extent than reactive companies a flexibility that is created by visions.</p>

Background: In recent research literature, some researchers mean that companies in fast changing markets have to act proactively while others find that companies have to adapt to conditions and to react. This makes it interesting to study how software companies act strategically and also to study to what extent a flexible organisation is required by companies who proact and by those who react. Purpose: The purpose of this thesis is the study how different types of software companies act strategically and what this requires of the company in terms of flexibility. Delimitation: The study treats only Swedish software companies with more than ten employees. Proceed of the Study: Representatives from four case companies as well as a consultant have been interviewed. As a complement to the case study, a survey has also been conducted where 36 companies have participated. Results: Only one of the four case companies can be said to act proactively. Among the survey companies, there are principally young companies, companies with a leading position on the market and companies that experience high growth that act proactively. Companies that work proactively value to a greater extent than reactive companies a flexibility that is created by visions.

The vast supply of different smartphone makes and models, along  with their  accompanying operating  systems,  increase the  demand  for  an  all-in-one  development  solution.   Quite a  few  approaches  to  solving  this  problem  have  cropped  up over the years, ranging from purely web-oriented solutions to something more akin to a native application.   React Native and Progressive Web App development are two different approaches,  both new and promising,  on this spectrum.   This thesis evaluates these approaches in a standardized way using the  ISO  25010 Product  Quality  Model to  gain  insight  into these  types  of  cross-platform  development  as  well  as  how well  such  an  evaluation  works  in  this  context.   The  results show that, while not a perfect fit, a standardized evaluation brings forward less obvious aspects of the development process and contributes with a helpful structure to the evaluation process.

This thesis contains present trends in frontend web development. On the basis of this, there is made web application which is responsive a it is usable on mobile devices. In the theoretical part, there are described news and present trends of frontend web development and in the practical part, there is described whole process, which contains design, development, testing and deployment. This thesis could be very useful for beginners in the subject.

In today's society, smartphones are so widely established that corporations have even changed their cooperate culture when it comes to bringing your own personal device to work. Sales graphs prove that smartphones are more established today than ever before, which creates pressure for companies big, as small to extend and provide their services from the pocket of the user in the form of a smartphone mobile application. This paper focuses on the development of smartphone applications. Looking into the native development way for iOS and the code fragmentation that characterizes the long and costly development in order to provide the application on the big mobile operating systems by evaluating the cross-platform solution React Native that bypasses the fragmentation. 
 The experiment presents the collected data and its solutions, with an evaluation of the React Native framework. Finally, thoughts and future work to further extend the category is presented.

No description available.

When developing mobile applications, the tradition has been to write code specific (native) for each platform they are running on. Usually it’s about writing two separate applications for the biggest platforms, Android and iOS. There exist alternatives to this approach that uses the same code for different platforms. React Native is a relatively new cross-platform development framework that makes it possible to use the same code for application to Android and iOS. It also uses native UI-elements as a possible solution for performance issues that is often associated with cross-plattform development. This thesis evaluates React Native and compares it against native Android. The implementation is done by replicating the main functionality from a social media application written as a native Android application. However, the application is not made as an exact replica since that could limit the solutions in React Native. The evaluation is done in a Startup company and therefore focuses on aspects important in a Startup. Another issue when developing a mobile application is what type of backend that shall be used. Performance, scalability and complexity are all important aspects when choosing a framework or language as a base for the backend architecture.There do exist theoretical frameworks that could be used when building the backend. However, these frameworks require resources that are often missing in a Startup. AWS Lambda is a platform that claims to be a cost-effective way of building a scalable application. In this thesis AWS Lambda is evaluated to see if it can be used to create an automatically scaled backend for this type of social media application. The conclusion of the React Native evaluation is that it can be a suitable alternative to native Android development. If the team has previous experience in web development but lack experience in mobile application development it can be a wise choice since it removes the need to learn two frameworks in native Android and native iOS development. React Native is also good to fast create functional prototypes which can be shown to potential investors. The biggest drawback is performance in animations. However, there are often ways to work around that. In our case this drawback did not affect the user experience of the end application. The evaluation of AWS Lambda concludes that it is not for every project. In this thesis, the application was a bit too database heavy and therefore the autoscaling ability did not work properly. However, for a service that needs a lot of computing power, AWS Lambda could be a good fit. It could also be a suitable alternative if someone in the team has previous experience in the AWS environment.

Today, there are many different ways to handle physical access control. RFID cards and tags are still a major solution but during the last years the market have been focusing on taking advantage of the devices that most people always carry with them, such as smartphones, tablets or smartwatches. This thesis has been carried out together with the company BRP Systems. They develop and deliver business systems to mainly the fitness business. In their product suite there is an application for booking workout sessions at these facilities. In this thesis their booking application has been rebuilt as a prototype and the functionality of unlocking the door and checking into workout sessions has been added. The application has been developed in React Native for Android and has been implemented in three versions using different techniques to sensor the users position at the door. The techniques are iBeacon, GPS and QR code. The iBeacon- and GPS versions work by allowing the user to unlock the door when standing outside it. A local notification will be pushed if the application is in the background. The QR code version allows the user to scan a QR code at the door to unlock it. When the door has been unlocked the users can also check into their booked workout sessions. The system and the different versions have been tested at one of BRP Systems customers to evaluate the usability. The conclusion is that an application with high usability can be built with all tested techniques in React Native. For the system to be used several other factors such as security and maintenance has to be considered. The choice to use React Native might be of high risk since it is a relatively new framework relying on community developed libraries.