With the smart handheld devices and the rapid development of network applications, data exchange between devices as the first problem. There are many ways the information can be transmitted from one end to the other end, but which one is the best way? This paper examines several common data package method, compare their features, advantages and disadvantages, and to test the effectiveness of the data package, the size of data packaged, the package needed time. In order to prove the practicality of packages, designed a "file synchronization system," using Protocol Buffer as data exchange formats, implementing the Android system.

The project has shown that it is possible to create applications for different mobile operating systems and linking the devices to the signal handler Data Engine . Using Qt as a framework and development environment allows doing this with only one code base, which can be made to work on different platforms. This creates great opportunity to save time and to reach a wider audience. The creation of a demonstrator application, a tutorial and a template for new projects has been the main goals for this project. These will serve as examples and guides for applications to come on how to deploy to mobile devices and connect to Data Engine using Wi-Fi. Though support for Windows Phone was not achieved, due to both development-wise difficulties and choices made during the project's course, the project was considered a success.

The introduction of mobile devices to the pockets and handbags of people living all over the world has made the practice of mobile computing nearly ubiquitous in modern society. iSeeMe is an Android application that empowers the user through the revelation of the vast amount of private data that mobile devices are capable of silently capturing in the background. iSeeMe strives to provide the user with a means to correlate this passively-collected information with data of personal importance to the user. This report looks into the development and implementation of the iSeeMe solution. It discusses design decisions, describes the iSeeMe architecture, and outlines the process of engineering the application. It also examines the role of personal data in modern society and explores the mobile application market to see where iSeeMe will fit in among similar applications. Finally, it analyzes the results of the development effort and identifies areas for future enhancement. / text

This report describes PlaceMe, a client side, mobile application built on the Android platform that provides personal location-based services such as location reminders, bookmarking, mapping and search nearby. The reminder system allows creating location based reminders, and alerts the user what he needs to do, when he is in the right place to do them. Bookmarking allows the user to virtually “save” places of interest while he is on the move and obtain driving directions. Mapping enables the user to visualize his relative geographic location in real time, and map the location reminders and bookmarks. Finally, search nearby exploits Google’s powerful local search engine to allow finding and bookmarking nearby places such as gas stations, restaurants, etc, and retrieving map-based directions. We first discuss the requirements and use-cases for PlaceMe, followed an introduction to the Android software stack. Next, we describe our design architecture, implementation model, test strategy and key performance enhancements. Then, we evaluate and compare the performance of the Android platform across a set of standard micro-benchmarks. Finally, we conclude with a discussion of future development ideas and present our thoughts on prospects of app-based mobile computing. / text

Smartphones are becoming increasingly popular, with the result that customers prefer to carry out at least some customer services using an app on a mobile device. Among app users, smooth transfer to a live agent is seen as an important feature and this means that the company contact center need a solution to handle this as well as increasing numbers of interactions. The question this thesis tries to answer is "how can smartphone end user apps be included in the context of the company contact center"? To answer this question research was conducted regarding the possibilities of an Android smartphone, with the results of this research being used to define a use case, a state flow diagram and create a demonstration app. The thesis showed that it is possible to have an app as an online channel for customer service interactions. New possibilities in comparison to traditional telephony include that customer data such as topic, authentication, location and multimedia can be sent to the contact center before an actual interaction is started.

Mobile apps can make use of the rich data and sensors available on smartphones to offer compelling services. However, the use of sensitive resources by apps is not always justified, which has led to new kinds of privacy risks and challenges. While it is possible for app market owners and third-parties to analyze the privacy-related behaviors of apps, present approaches are difficult and tedious. I present two iterations of the design, implementation, and evaluation of a system, Gort, which enables more efficient app analysis, by reducing the burden of instrumenting apps, making it easier to find potential privacy problems, and presenting sensitive behavior in context. Gort interacts with apps while instrumenting them to detect sensitive information transmissions. It then presents this information along with the associated app context to a crowd of users to obtain their expectations and comfort regarding the privacy implications of using the app. Gort also runs a set of heuristics on the app to flag potential privacy problems. Finally, Gort synthesizes the information obtained through its analysis and presents it in an interactive GUI, built specifically for privacy analysts. This work offers three distinct new advances over the state of the art. First, Gort uses a set of heuristics, elicited through interviews with 12 experts, to identify potential app privacy problems. Gort heuristics present high-level privacy problems instead of the overwhelming amount of information offered through existing tools. Second, Gort automatically interacts with apps by discovering and interacting with UI elements while instrumenting app behavior. This eliminates the need for analysts to manually interact with apps or to script interactions. Third, Gort uses crowdsourcing in a novel way to determine whether app privacy leaks are legitimate and desirable and raises red flags about potentially suspicious app behavior. While existing tools can detect privacy leaks, they cannot determine whether the privacy leaks are beneficial or desirable to the user. Gort was evaluated through two separate user studies. The experiences from building Gort and the insights from the user studies guide the creation of future systems, especially systems intended for the inspection and analysis of software.

Fjärrstyrning av värmepumpar är en bekvämlighet för att slippa vara på plats och ändå kunna göra inställningar på sin värmepump. Det ger möjligheten att komma till ett förvärmt fritidshus eller stuga med några enkla knapptryckningar. Det ger också möjligheten till mer kontroll över pumpens energiförbrukning, man kan spara in pengar på att inte låta pumpen stå och slösa energi då man inte är på plats. I dagsläget finns flera fjärrstyrningsprodukter för värmepumpar på marknaden, men dessa är ofta dyra och kan oftast bara ansluta till mobilnätet eller wifi. Fjärrstyrningsprodukterna är speciellt framtagna för att styra en värmepump och kan ej användas för att styra ytterligare produkter. Målet med detta examensarbete är att ta fram ett system baserat på en standardplattform som åtgärdar dessa problem samt där det finns möjlighet till framtida utbyggnad av dess funktionalitet. Vi börjar med att bestämma funktionaliteten för vår fjärrstyrningsprodukt. Därefter tas en struktur för hela systemet fram. Efter detta görs val av hårdvara och mjukvaruutveckling. Resultatet av vårt examensarbete är en fjärrstyrningsprodukt som kan styra Daikins värmepumpar. Vår fjärrstyrningsprodukt kan använda 3G-nätet, wifi eller trådat nätverk för att kommunicera med vårt systems centralenhet och användaren. Vår produkt har även en stor potential till utbyggnad för fjärrstyrning eller övervakning av andra enheter i hemmet.

Kriminalvården är den myndighet i Sverige som ansvarar för fängelser, häkten och frivård. Myndigheten har länge känt ett behov att inom flera verksamheter kunna få tillgång till delmängder av deras klientsystem i ett mobilt och uppkopplat format. Det största hindret i deras fall med mobilitet och applikationsteknik var säkerheten. Därför genomfördes en riskanalys med hänsyn till frivården och mobilapplikationsteknik. För att välja en lämplig och passande riskanalysmetod jämförde vi ett antal metoder. Det visade sig att metoden CORAS passade bäst. När vi väl genomfört riskanalysen med CORAS försökte vi sedan matcha åtgärderna mot de olika mobilplattformarnas egenskaper för att se hur de kan fullfölja åtgärderna. Mobilplattformarna vi undersökte var Android, Windows Phone 8 och iOS. Resultatet av riskanalysen och jämförelsen av plattformar kan ligga som grund till beslut hos Kriminalvården. / Kriminalvården is the government agency in Sweden which is responsible for prisons, jails and probation. The agency has realized a need of access to a several features of their inmate register systems from mobiles and handsets within different areas in their organization. The safety with the mobility and application technology is a comprehensive issue in this case. Therefore, a risk analysis about mobile application technology was initiated. We took the probation services into account as a concrete scenario where mobile application technology could be used. In order to select an appropriate and adequate risk analysis method, we compared a number of methods. It turned out that the method CORAS was the most suitable method. When we completed the risk analysis with CORAS, we tried to match the treatments against different mobile platforms properties to see how they can pursue the treatments. Mobile platforms we examined were Android, Windows Phone 8 and iOS. The result of the risk analysis and the comparison of mobile platforms can the agency use as a basis for further decisions.

Den här studien undersöker för- och nackdelar med att migrera existerande mobilaapplikationer till Xamarins crossplatform ramverk Xamarin Forms. Metoden somanvänts för att samla in data är inom ramen för forskningsparadigmet Design Science.En prototyp har utvecklats med syftet att undersöka vad som är möjligt att migrera tillXamarin Forms. Prototyputvecklingen har dokumenterats i loggböcker som sedananalyserats som kvalitativ data. Två intervjuer har även genomförts med andraxamarinutvecklare med syftet att nå en djupare förståelse för ämnet. Studien harproducerat ett flödesschema för när ett beslut om att migrera en existerande applikationtill Xamarin Forms bör tas. Vid beslut om migration har vi även formulerat ett antalriktlinjer som bör efterföljas för att uppnå bra resultat. Flödesschemat och riktlinjerna ärbaserade på resultaten från analysen av loggböckerna och intervjuerna. / This study investigates the pros and cons of migraiting existing mobile applications toXamarins crossplatform framework Xamarin Forms. The method that is being used tocollect data is within the scope of the research paradigm Design Science. A prototype ofan existing mobile application has been developed in order to research the possibilitiesof migraiting existing applications to Xamarin Forms. The development process of theprototype has been documented in journals which later were to be analyzed asqualitative data. Two interviews have been done with other Xamarin developers in orderto get a deeper understanding of the subject. This study produced a flowchart that is tobe used when deciding about a migration of an existing mobile application aswell asguidelines for the migration itself. The flowchart and guidelines are based on analyzingthe data from our journals aswell as our interviews with other developers.

Developing apps for both Android and iOS has previously necessitated two different code bases in the platforms’ native languages. Creating an app would be a quicker and easier process if they could be written once and run on both platforms, and such solutions have been appearing over the last few years. One of them is React Native, which we will investigate in this paper. To investigate React Native’s capabilities, we are going to look into the feasibility of porting the Android and iOS versions of an already existing fitness app, developed by a software consulting company. The original app uses Bluetoothfunctionality to record users’ heart-rate during exercise. They want to know if they can switch to React Native and a single code-base for future installments, lessening the workload and making it more maintainable. In order to find out if it is advisable to recreate the app with React Native we attempt a port of the app, looking at performance, functionality, and the codebase. The code-base investigation focuses on what parts can become completely platform independent and where we need to fill in the gaps with code targeted to a certain platform, and how large our port is in relation to the equivalent code in the original app. We end up finding that performance is severely worse on iOS, with much higher CPU utilization when the Bluetooth functionality is in use. On Android the difference is noticeable but not quite as big. For functionality we could get everything working with a single code-base except for handling Bluetooth while the app is in the background on Android. The code-base is mostly platform independent, and where it is not this is due to differing Bluetooth implementations for the platforms. It is also larger than either of the original apps, but smaller than the two put together. Lastly, we conclude that React Native has a largely platform-independent codebase, and for simpler apps where less complex functionality is needed we suspect the code-base can be completely platform-independent. The cause and remedies to iOS performance ought to be further investigated, but React Native is capable for this particular use-case.