User interfaces are a crucial point in the usage of products. A user interface is developed to make a product easy to use and understand while also presenting data, feedback and functionality to the user. In this thesis we present and explain the whole development process of a front end project. The Swedish company, Kemizares, was searching for a user interface for their finance module in their upcoming application. In this work we developed the user interface for such a module with regards to Kemizares’ functional requirements as well as the necessity that the user interface of the module could be integrated into the their application which already had an existing user interface. The solution to the problem began with a literature study in which we researched tools and programs we would use to develop the module as well as researching national and international requirements for invoices to identify necessary data to use in the finance module. Afterwards we set up a timeline with deadlines to guide us throughout the development. An agile iterative feedback method was used during the implementation of the module with Kemizares. The finance module was created and with the iterative feedback method we used during development we were able to ensure that Kemizares was satisfied with the product. However, due to limiting factors we were not able to finish the whole module and hence not able to fulfill all the requirements. The conclusion is that the module in its current state is not a viable solution for Kemizares since it was left undone but a good ground to continue from that has taken required financial data, functional requirements, and design compatibility with the rest of the application into consideration. / Användargränssnitt är en viktig punkt i användningen av produkter. Ett användar-gränssnitt är utvecklat för att göra en produkt enkel att använda och förstå samtidigt som den presenterar data, feedback och funktionalitet för användaren. I denna rapport presenterar och förklarar vi hela utvecklingsprocessen för ett frontend-projekt. Det svenska företaget Kemizares letade efter ett användargränssnitt för sin finansmodul i sin kommande applikation. I detta arbete utvecklade vi användargränssnittet för en sådan modul med avseende på Kemizares funktionella krav samt behovet av att modulens användargränssnitt kunde integreras i deras applikation som redan hade ett befintligt användargränssnitt. Lösningen på problemet började med en litteraturstudie där vi undersökte verktyg och program som vi skulle använda för att utveckla modulen samt undersökte nationella och internationella krav på fakturor för att identifiera nödvändiga data att använda i finansmodulen. Därefter satte vi upp en tidslinje med deadlines för att vägleda oss genom hela utvecklingen. En agil iterativ återkopplingsmetod användes under implementeringen av modulen med Kemizares. Finansmodulen skapades och med den iterativa återkopplingsmetoden som vi använde under utvecklingen kunde vi säkerställa att Kemizares var nöjd med produkten. Men på grund av begränsande faktorer kunde vi inte avsluta hela modulen och kunde därför inte uppfylla alla krav. Slutsatsen är att modulen i sitt nuvarande tillstånd inte är en lönsam lösning för Kemizares eftersom den lämnades ofärdig, men en bra grund att fortsätta från som har tagit hänsyn till nödvändiga ekonomiska data, funktionella krav och designkompatibilitet med resten av applikationen.

Context: Flatbed applicators are machines made for laminating, primarily signs on an industrial level. These applicators are controlled manually, which exhibits potential for digitalization in order to enhance the user experience. Problem: The first challenge is to develop a user interface for a mobile app, created to provide an easy path for communication to customers, with user-friendliness as the focal point. The second challenge is being able to communicate with a flatbed applicator, through the aforementioned app. Method: This project started out with pre-studies about the required topics. The system prototype was then designed and implemented with a focus on adequate UI design guidelines for the mobile app and a suitable protocol to enable communication between the app and the applicator. Results: The app prototype was developed through the usage of J.J. Garrett’s model along with Material Design guidelines, in order to establish a customer-centric user interface. Communicating between the mobile app and a PLC using TwinCAT, MQTT and React Native appears to be a feasible solution.

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.