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.

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.

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.

Unmanned aerial vehicles can be used in many different situations such as, for example, monitoring the growth of crops or for surveillance of a private property. Operating the unmanned aerial vehicle is usually done using some kind of ground control station. This thesis examines the possibilities of creating ground control stations working on several different platforms using the cross platform development frameworks Xamarin, Universal Windows Platform and Mono. This is done by creating and comparing three prototype applications regarding functional requirements, code reuse and resource usage. It is shown that none of the cross platform frameworks can fulfill all of the initial requirements on a ground control station. However, for the case studied in this thesis, Xamarin is demonstrated to be the most suitable cross platform framework of the three since it provides the same functionality as UWP for Windows devices while also enabling development for both Android and iOS devices.

In the industry there is a need for a more efficient way to troubleshoot machines that uses the protocol EtherNet/IP. The current methods is time consuming and complex. This project gather data from a simulated network and analyze the data. The result of the analyze is presented on a cellphone application with a description and a possible solution. The application is a cross-platform application developed with Cordova. The simulated network is created on a Raspberry Pi 2. The analyze is done on another Raspberry Pi 2 running the software Node-RED. Communication between the simulated network Raspberry and the cellphone is with Bluetooth Low Energy. Communication between cellphone and the server is with MQTT. There are several areas where this kind of application may suit. This project is in one specific area – troubleshooting EtherNet/IP.

Developing applications for mobile devices is nowadays a very large business. However, the process of developing an application can be both very time consuming and costly due to different languages used for different devices. Lately, a lot of tools have been developed to handle the different languages problem going under the name “cross-platform” - so many that it might get hard for the developer to make a choice between the different products. This thesis presents 4 different approaches for programming cross-platform applications: Web based, cross-compiled, interpreted and hybrid solutions. For each category, one product is chosen and is evaluated according to comparison tests suggested in the thesis, including benchmark tests, technical evaluation tests seen from both the developing perspective and the infrastructure perspective and last a functionality evaluation. Other important parameters to think about when developing an application are also presented. At the end of the thesis, a taxonomy of applications is presented in order to give examples when a cross-platform solution is suitable and which cross-platform tool should be used. Finally, there are some important points taken up about what the developer should think about, when choosing a solution according to this thesis as there is no straight forward way to say that one cross-platform solution is the best of them all. / Utvecklandet av mobila applikationer är idag en väldigt stor marknad, men utvecklingsprocessen kan ibland vara både tidskonsumerande och kostsam eftersom de olika mobila enheterna använder olika utvecklingsspråk. Den senaste tiden har många verktyg utvecklats för att hantera detta problem, dessa verktyg ingår i kategorin cross-plattform verktyg. I själva verket är det så många verktyg som har utvecklats att det kan bli svårt för utvecklarna att välja mellan de olika verktygen. Denna uppsats presenterar 4 olika tillvägagångssätt för att programmera cross-plattforms applikationer: web baserade lösningar, hybrid lösningar, översatta lösningar och cross-kompilerade lösningar. För varje kategori väljs sedan en produkt, som skall evalueras enligt ett jämförelsetest som denna uppsats föreslår, detta test inkluderar ett benchmark test, en teknisk evaluering och en funktionsevaluering. Förutom dessa test ges även andra viktiga parametrar gällande cross-plattforms utveckling. I slutet av uppsatsen är en taxonomi av mobila applikationer presenterad vars syfte är att ge exempel när ett cross-plattforms verktyg är passande för en mobil applikation, och även vilket verktyg som är passande. Slutligen tas några viktiga punkter upp som utvecklaren bör tänka på när ett cross-plattforms verktyg skall användas för utveckling, eftersom det inte finns något direkt sätt att säga att ett cross-plattforms verktyg är bättre än ett annat.

Syftet med undersökningen är att jag ska samla kunskap om olika ramverk för att ta fram hybridapplikationer och undersöka hur dessa ramverk presterar mot kriterier som tagits fram tillsammans med Bulldozer kommunikationsbyrå. Med hjälp av en samling kriterier är målet med undersökningen att komma fram till vilket som är det “bästa” ramverket för att ta fram en hybridapplikation för en webbutvecklare som saknar kompetens för att utveckla plattformsspecifika applikationer. Resultatet ska vägleda målgruppen i vilket ramverk de ska använda sig av när de bestämmer sig för att börja utveckla applikationer. Datainsamling för undersökningen skedde i två omgångar. Den första var vid urvalet av ramverk och då åtta stycken ramverk blev tre genom en dokumentanalys. Den andra omgången av datainsamling skedde på applikationerna som utvecklades utefter vilka tre ramverk som samlade på sig mest poäng under första datainsamlingen. Hur lätt det kommer att vara att underhålla och sätta sig in i koden undersöktes bara på de skrivna applikationerna och mättes med hjälp av cyklomatisk komplexitet och logiska rader kod. De ramverk som samlade på sig mest poäng efter första urvalet var Meteor, Phonegap och Titanium. Titanium valde under undersökningens gång att bli kommersiellt och täckte därför inte längre kriterierna och därför utvecklades det ingen applikation för det ramverket. Det utvecklades istället en applikation på ramverket som samlade på sig fjärde mest poäng, Cordova. Av Meteor, Phonegap och Cordova är Phonegap att föredra även om det samlade på sig lika många poäng som Meteor. Detta för att Phonegap är mognare och koden är mindre komplex vilket gör den lättare för utvecklare att sätta sig in i och hantera.

Today's living room context offers more and more possibilities when it comes to when and how to interact with the television and media content offerings. Buzzwords such as "TV Everywhere" is something that both hardware manufacturers, content providers and television networks are pursuing to great lengths. At the core of such marketing schemes is the availability of platform-independent content consumption. In a Utopian setting, the end-user should never have to worry if he or she is currently using a smart TV, tablet, phone or computer to view a video or photos, play music or play games. Taking the concept even further, the devices should also be able to connect and communicate with each other seamlessly. Having for example a television set (first screen) controlled by a mobile phone (second screen) is commonly referred to as companion device interaction and is what this thesis has investigated. More specifically, a way of discovering and launching a first screen application from a second screen application using the zero configuration discovery protocol named DIAL has been implemented into a cross-platform messaging solution. A case study was conducted to gather data about the system and its context as well as what was needed of the framework in terms of architecture design, use cases and implementation details. A proof of concept application was developed for Android that used the proposed framework, showcasing the ease of use and functionality presented in integrating DIAL into such a solution. Since DIAL is so well-documented, easy to understand and is becoming one of the industry standards among consumer electronic manufacturers in terms of device discovery, I believe it should become a standard for so called zero configuration companion device interactivity.

In this thesis, we present a tool that is an extension of the NAVIRE Framework and used in remote environment exploration and navigation. It is available for end users on everyday devices such as desktops and mobile devices. The tool offers the characteristic of being cross-platform and easy to use and manipulate. Cubic panoramas that are generated by the NAVIRE Framework are loaded in the tool and rendered in 3D space on the user’s device. The 3D panoramas are interactive by allowing the user to view the scene in all direction, move from one scene to another or through interaction with augmented objects. The tool is geared to be interactive in the most natural and intuitive fashion using the inputs available in the different devices of the end-user.

The number of available mobile applications (or apps) as well as the usage of these are rapidly increasing. With this increase there naturally also follows an increased competitiveness in the app market, with developers needing to produce apps of high perceived quality in order to get return users and also needing to make their apps available to multiple different platforms and devices. With substantial platform and device fragmentation, this is often a difficult and costly task. While traditionally an app basically had to be build from scratch for each platform it needed to support, in later years alternative development techniques for what is called cross-platform development have emerged and seen a rapid increase in usage. Contrary to native development, cross-platform development aims to enable development of a single codebase that can then run on all platforms. The idea is that this would save development time and thereby cost. Academic literature was found to often evaluate and compare performance differences between apps developed with cross-platform frameworks and their natively developed counterparts. Typically, these studies reported several reoccurring drawbacks with cross-platform development, compared to native development. However, research within the field was found to be lacking in regard to developers’ experience in general, and specifically whether this focus on comparing performance and listing pros and cons was representative of the concerns of industry developers. This study aimed to begin filling this gap, byinvestigating the extent to which these developers were relating any drawbacks to cross-platform development as well as which these were. Also, the study sought to answer how big a part this awareness of drawbacks played in the decision when developers chose to develop natively instead of cross-platform. With this, the goal of the study was ultimately to discussthe state of cross-platform research and whether it focused on aspects that were relevant to the industry. Data in this study was gathered in two ways: (1) a literature study, aiming to get an image of the current state of cross-platform research and (2) a web survey, in which app developers were invited through various groups in Facebook and Reddit. Ultimately, the results indicated that industry developers were to a large extent relating the same drawbacks to cross-platform development as were found to be frequently reported by academia. Further, all of the survey participants that related drawbacks to cross-platform development and ever chose to develop natively instead of cross-platform, did so to a very large degree because of those drawbacks. There were limitations to both the planning and the execution of the methods that were used, primarily in the gathering of data but also the analysis of this. However, it was still deemed possible to conclude that the results of the study indicated that research regarding cross-platform development could reasonably keep its current focus moving forward, as this appeared to be of high relevance to the industry.