Människan-datorinteraktion (HCI) är ett studieområde som fokuserar på design av datorteknik, särskilt interaktionen mellan människor (användarna) och datorer. Detta projekt beskriver utveckling av en webbapplikation (React) för kunder att göra sina onlineköp. Syftet med projektet är att använda interaktionsdesign och användbarhetsmål för att skapa en applikation för konsumenter. Målet var att studera hur react användas för att ta fram en en färdig produkt.För att bygga produkten bör interationsdesign kunna ha en välfungerade app. Interationdesign används för att skapa en bra användarupplevelsen.Annvändbarhet gjordes för att möta andvändarens behov. Detta system kommer att tillåta hotell och restauranger att underlätta användarnas tid under mat beställningsprocessen. Användare kunde testa appen och lämna deras förslag och feedback. Avslutningsvis, att använda react för applikationen var ett bra val och genom interaktionsdesign kunde applikationen utföra sina uppgifter framgångsrikt. När man utvärderade appens användbarhet, var fler än genomsnittet av användarna nöjda och kunde använda webbapplikationen utan svårighet. Applikationen kan vidareutvecklas i framtiden för att förbättra användarupplevelsen och fler funktioner kan tilläggas för att uppfylla kundens behov. Implementering av backend (servrar och databaser som är inte synliga för användarna) kommer också att vara ett plus för Appen i framtiden. / Human-computer interaction (HCI) is a field of study focusing on the design of computer technology, in particular, the interaction between humans (the users) and computers. This project describes the development of a web application (React) for customers to make their purchases online. The purpose of the project is to use interaction design and usability goals to create an application for food lovers. The aim is to study how react can be used to produce a finished product. To build the product, interaction design should be able to have well function app. Interaction Design principles is used to have a great user experience. Usability was done to meet user’s needs. This system will allow hotels and restaurants to ease users' time during the food ordering process. Users were able to test the app and their suggestions and feedback. In conclusion, using react for the application was a good choice and through interaction design the application was able to do its tasks successfully. Evaluating the usability of the app, more than average of the users were pleased and able to use the web application at ease. The application can be further developed in the future to improve the user experience and more functions can be added to satisfy customer’s needs. Implementation of backend will be also a plus for the App in the future

Användare har blivit mer och mer otåligare genom tiden, nu kan en användare tappa fokus efter bara några sekunder. För att möta detta undersöktes olika JavaScript bibliotek över vilken som har kortast renderingstid. Med hjälp av en Leaderboard för en träningsapplikation, som ger en Gamification effekt och kan leda till att användare vill öka sin fysiska aktivitet. Ett sätt att presentera ledningen i en leaderboard är via ett stapeldiagram. Denna studie undersöker tre olika visualiseringsbibliotek som jämför tiden det tar att rendera fram ett stapeldiagram. Applikationen är i grunden en React applikation med de tre visualiseringsbiblioteken som React komponenter. Resultatet slutade med att Hypotesen stämde med att det finns en statistisk signifikant skillnad mellan visualiseringsbiblioteken. Resultatet visade också på att D3 hade det kortaste renderingstiderna för denna studie. För framtida arbete skulle ytterligare mätningsmetoder prövas, om det finns bättre mätningsmetoder för att jämföra det tre olika visualiseringsbiblioteken.

Idag finns det många olika metoder för att bygga appar. Det är möjligt att utveckla separata appar för samtliga plattformar eller att använda något av Cross Platform-ramverken. Då de olika metoderna har både för- och nackdelar är det av vikt att välja den bästa metoden för just sin app. Under detta arbete kommer en app att skapas med två olika metoder. En med Cross Platform-ramverket React Native samt en motsvarande webbaserad app, närmare bestämt en Progressiv Webb App (PWA) skriven i React. Därefter kommer en jämförelse av tre funktionaliteter (kamera, bluetooth-skanning och NFC-skanning) att utföras för att besluta vilken av dessa appar som gav det bästa resultatet samt arbetsbördan ur ett utvecklarperspektiv. De främsta problemen som uppstod var stylingproblem, kamerafunktionalitet samt att vissa webbmotorer inte tillåter bluetooth- och NFC-skanning. Detta innebar att dessa funktionaliteter inte fungerar på alla webbläsare. Resultatet indikerar att PWA har sina begränsningar när det kommer till hårdvarunära funktionalitet, men är i övrigt ett mycket bra sätt att bygga en app på. React Native är bättre när det kommer till hårdvarunära funktioner men kan leda till fler stylingproblem. / There are many different ways to create apps these days, one can choose to create separate apps for each platform or use a Cross Platform framework. Because different methods have different benefits and drawbacks, it is critical to find the best method for your specific app. This project will result in the development of two apps: a Cross Platform React Native app and a web-based app, dubbed a Progressive Web App (PWA) written in React. Following that, a comparison of three functions (camera, bluetooth scanning, and NFC scanning) will be carried out in order to determine which of these frameworks provided the best results and workload from an engineering perspective. The most serious issues that arose were styling issues, camera functionality, and the fact that some web browser engines do not support Bluetooth or NFC scanning, implying that these features do not work on all browsers. PWA has its limitations when it comes to native features, but it is still a very good way of building an app. When it comes to native features, React Native is better, but it can lead to more stylistic issues.

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.

Den här rapporten behandlar arbetet utfört av sju studenter på Linköpings universitet som går programmen civilingenjör i datateknik och mjukvaruteknik. Rapporten är en del av kursen TDDD96 Kandidatprojekt i programutveckling under vårterminen 2018. Arbetet har omfattat utveckling av webbapplikationen Placeholder, på uppdrag av Niclas Hjorth vid Röntgenkliniken Linköping. Applikationen som utvecklades är ett verktyg skapat för att underlätta schemaläggningen av personalen på röntgenkliniken. Schemaläggarens jobb underlättades genom funktionalitet som att tydligt visa var personer är inbokade samt vilka personer som finns tillgängliga. Arbetssättet följde en anpassad och avskalad variant av Scrum. Utvecklingsarbetet har utförts inkrementellt och iterativt med delleveranser av produkten i form av prototyper under projektets gång. Arbetssättet resulterade i att projektets arbete har kunnat anpassats efter ändringar i kundens önskemål om funktion. Projektet resulterade i en prototyp för kunden som kan användas för fortsatt utveckling. Under projektets gång upplevde gruppen erfarenheter som fångats upp, dessa erfarenheter visade på att kommunikation i projekt är viktiga. Gruppen visade även att Trello är ett användbart verktyg för agil systemutveckling

The traditional or the native way to develop mobile applications is to use Java for Android and Objective-c or Swift for iOS. The native way is favored by many since the code and the functionality is optimized for the platform. An- other way to develop mobile applications is to do it the non-native way, with a programming language or technique not made for the platform. This approach has for long been frowned upon due the limited hardware access and perfor- mance loss. React Native and NativeScript offers mobile application develop- ment in a non-native way said full access to the native platforms API using JavaScript all from a single code base. The aim of this thesis has been to de- velop and compare four proof of concept applications of which two are devel- oped natively for Android and iOS and the other are developed using the non- native React Native and NativeScript. The comparison is based on three as- pects: accessing the device’s native hardware and APIs based on what the com- pany Dewire requires from mobile applications, the performance difference on the respective platform and code reusability cross platform. There is no big dif- ference between React Native and NativeScript when comparing native access and everything that was accessible on the native implementation was accessible on the non-native implementation. Based on the performance measurements, React Native falls behind NativeScript. NativeScript handles long lists better than React Native. Lastly a discussion is presented regarding code reusability when developing non-native applications along with some experienced best practices when doing so.

A big problem with mobile application development is that the mobile market is divided amongst several platforms. Because of this, development time gets longer, more development skills are needed and the application gets harder to maintain. A solution to this is cross-platform development, which allows you to develop an application for several platforms at the same time. Since September 2015 the cross-platform framework React Native, created by Facebook, has been available for public use. This thesis evaluates React Native, for both Android and iOS, in regards to performance, platform code sharing as well as look and feel. An application was developed for both platforms, one version using the native language and one version using React Native. The different versions were compared through automated test scenarios to evaluate performance, manual code review for platform code sharing and with a user study to evaluate the look and feel. The results show promise as the user study shows that the React Native versions of the application have similar user experiences as their native counterparts without significantly affecting performance. The results also show that for the specified application about 75% of the React Native code could be used for both platforms, while it was easy to add platform-specific code.

This thesis deals with the theory of creating modern web applications. Various technologies that are commonly used are analyzed. Thesis mainly deals with creating specific application for processing Warranty Claims. The application serves as a service for eshops.

This diploma thesis focuses on development of graphical user interface for managing IVR applications. The work is more software oriented, it analyzes current state of the iPBX product belonging to the IPEX a.s. company, describes used technologies and introduces new concept of interactive user interface for generating IVR diagrams together with Asterisk dial plan generator.

The main goal of this master's thesis was development of Burp Suite extension capable of interacting with various other automated tools, accompanied with development of a web application. Chapter two contains analysis of tools commonly used in penetration testing that could benefit from the ability to share Burp Suites data or functionality. The programming languages used were Java and JavaScript. The extension acts as a gateway to inner functionality of Burp Suite. It enables exfiltration of in memory objects such as sitemap, proxy history or found issues in JSON format to other tools, and also listens for incoming data that can be inserted into it's existing modules such as Repeater, Scanner, Spider or Comparer. Frontend application was written using JavaScript library React. The web application offers a graphical visualization of issue data.