Since the third-generation’s mobile telephony was introduced, the use of the Internet changed significantly. Websites can nowadays be viewed from a wide range of devices that differ in type and size. This puts a demand on the design of web pages because the page should be equally useful regardless of the type of device used to view the page. Responsive web design is a design method that strives towards solving this problem by allowing web pages to customize their visual representation based on the medium used to interact with them. Although it is a well-used tool in web development, it is relatively unexplored from a technical, aesthetic and functional perspective. The goal of this thesis is to improve the situation by exploring the possibilities and limitations of responsive web design in relation to the above perspectives. To achieve this, common definitions of this approach were collected, together with an implementation of a responsive product. To give structure to the analysis, the development process followed the Double Diamond approach together with two experiential qualities, fluidity and naturality. By using media queries together with scalable units in the implementation, a fully responsive portfolio website was created. The creation of the product gave room for understanding possibilities and limitations of responsive web design. The encountered problems in this thesis, such as detecting different types of devices, concludes that responsive web design is yet not a fully developed approach and contains problems that limit the implementation.

This paper describes a usability study of a responsive website prototype. A heuristic evaluation was conducted with three evaluators with a background in HCI, and user tests with four potential users were conducted as a control method to test the relevance of the heuristic evaluation result. The study showed that the website prototype failed the visibility of system status, user control and freedom and error prevention heuristics in the heuristic evaluation. However, the users responses contradict that result by showing that the users had no problems with those areas in the user tests. In fact, the users detected no usability problems at all. This could mean that those heuristics are not relevant for a responsive Web 2.0 site and needs to be removed when conducting a heuristic evaluation of a responsive website in the future, and that designing for responsiveness leads to higher usability. This study shows some indications but more testing needs to be done, preferably on several fully developed responsive websites, to be able to make any real conclusions about the usability of a responsive website and the relevance of the heuristics used in this study.

The IT industry is constantly evolving and requires everyone working with website development to be updated on the latest methods. The web grows larger every day, and more visits are carried out by mobile devices. It is more important than ever for companies to have updated and functional pages that can be used on different platforms. We want to find out how common it is for IT departments and web agencies to embrace the newest technology and also what it takes to get them to move from one technology to another. Responsive web design is a constantly growing new technique that helps web developers developing for different platforms. In this paper we have chosen to use responsive web design as an example in our research on how new technology is implemented in different companies.

Technologies for how a rich user interaction can be delivered have changed a lot during the last 10 years. From a world where these types of user interfaces predominately was built as desktop applications like Windows Applications over to web technologies using Java Applets, Flash, Silverlight, Android, iOS etc. The problem though has been the vast amount of different technologies with no or limited connections between them. This has so far been a problem for application developers since essentially no code can be reused between the different platforms but also that some of them are not native – some kind of runtime platform needs to be installed (Flash, Silverlight, Java…). With the introduction of the emerging standard of HTML5 it seems that there is finally a technology that is getting more widely used by most of the platform suppliers.  This Master Thesis aims to prove the HTML5 can be used to build clients for MediusFlow. The point is to investigate if it’s possible to implement all the pages of frontend on different platforms by using idea like Responsive Web Design with HTML5.The showcase will be to build a complete app for MediusFlow on the iPad platform based on HTML5. In addition the interface must be verified on at least one additional platform, most probably Internet Explorer 10.

Responsive Web Design (RWD) har på kort tid gått från ett koncept till en av de största trenderna inomwebbutveckling. Det är nästan underförstått idag att nya webbsidor ska vara i RWD. Trots det är inte RWD detsjälvklara alternativet som löser alla problem dagens utvecklare står inför när det gäller den stora floran av surfandeenheter. I examensarbetet djupdyker vi i tekniken, både praktiskt och teoretiskt, för att kunna dra slutsatser om RWDs styrkoroch svagheter. Detta åstadkoms genom att ta fram en applikationsplattform och en första applikation(semesterplanering) åt konsultföretaget Sigma AB, där ett av grundkraven var att det vi utvecklade skulle kunnaanvändas varsomhelst. Utifrån våra resultat lämnas rekommendationer på när RWD är alternativet att satsa på och när det behöverkompletteras av andra tekniker, så som Native- eller HTML5 applikationer. / Responsive Web Design (RWD) has quickly moved from a concept to one of the biggest trends within WebDevelopment. Today it is close to implied that new Websites should use the technique RWD. Even so the techniquedo not cover all problems the developers are facing today when it comes to the flora of mobile devices. Within this thesis we are digging deeper into the technique, both in practice and theory, in order to make conclusionson its advantages and disadvantages. This we fulfilled by creating both an application platform and a first application(to handle vacation requests) for the company Sigma AB, there one of basic requirements were that everythingdeveloped could be used anywhere. From our results we are giving recommendations for when you should use RWD and when you should considerother techniques like Native- or HTML5 applications.

This master thesis focuses on approaches to solving mobile web applications. Author focuses on the classification of mobile devices and the description of their attributes and specifications of touch screen controls. Part of the work is devoted to the characteristics of mobile operating systems and of mobile web browsers. One chapter is aimed on the psychology of user behaviour and expectations of mobile users from mobile website. A significant part of the work is paid to specifications of the development of web design for mobile devices and the differences to classical web design. In addition, the author describes the Responsive Web Design and the idea of Mobile First. In the practical part, the author analyzes the cross platform access to websites of Czech railway transport companies -- České dráhy, LEO Express and RegioJet. The access from smartphones, tablets and desktops is tested using analysis based on multi-criteria evaluation. To test the author uses a web emulator to simulate different versions of operating systems and web browsers. The aim of the analysis is to create a series of recommendations for better optimization of access from mobile devices.

Before Responsive Web Design (RWD) it was common to create fixed-width websites. In recent years the standard way of creating responsive websites is by some of the fundamental aspects of RWD on the client-side. But can it be worth using RWD with components sent from a server by detecting the device and send component-specific material as to lessen some of the resources of the page? Tests have been made for this purpose with Google Lighthouse’s performance audits in mobile and desktop mode between four almost identical websites. These tests measures which website will receive better load-time performance results viewed from an emulated smartphone with a 3G/4G connection (mobile) and an emulated desktop PC with a 10 Mbps of connection (desktop). Each website consists of two pages, one with lesser resources (< 1 MB, known as index.html), the other with larger resources (24.3 MB, known as gallery.html). All four websites are responsive and built after the main pillars of RWD. Two websites does not have any optimization while two websites have added image optimization. One of the two websites in each category, image-optimized and unoptimized, is a server-based component website. This means, it will use asynchronous calls to a server to get specific components for the specific viewport.  In the tests performed, between the unoptimized websites, one client-based (CRWDu), the other server-based (SRWDu), on index.html, the CRWDu website scored best in mobile and got a slightly better result in desktop mode. On gallery.html, the SRWDu website received the best results in both modes, mobile and desktop. Between the image-optimized websites, one client-based (CRWDo), the other server-based (SRWDo), the CRWDo website on index.html, had a slightly better result in mobile and a worse result in desktop mode. On gallery.html, the SRWDo website had a much better result in both mobile and desktop mode.

The presentation of the search result information has become more important ever since the rapid development and use of smartphones. This thesis investigated what makes search engine result pages efficient and effective on the smartphone screen. For this thesis an experimental study of Karolinska Institutet’s search solution was executed. Three different versions of Karolinska Institutet’s search engine result pages were developed, by researching potential features that would improve the effectiveness and efficiency. The developed versions were compared to the original search engine result pages through experiments with students from Karolinska Institutet. The quantitative results showed no statistical significance of improvement in effectiveness or efficiency. The qualitative results indicated that categories and summary texts are preferable features in a search GUI in a smartphone. Thus the results were indecisive, the author reflects and provides ideas on how to achieve clearer results. / Hur man presenterar sökresultat har blivit allt viktigare i och med dagens av smarttelefoner. Det här arbetet undersökte vad som gör sökresultatssidor effektiva när man använder en smarttelefon. I arbetet utfördes en experimentell studie av Karolinska Institutets söklösning. Tre olika versioner av Karolinska Institutets smarttelefonsgränssnitt utvecklades genom att undersöka potentiella \emph{features} (funktioner, egenskaper) som förbättrar effektiviteten. De olika utvecklade versionerna jämfördes mot det original som Karolinska Institutet använder idag. Detta gjordes genom experiment med studenter från Karolinska Institutet. De kvantitativa resultaten kunde inte visa på någon statistisk signifikant effektivitetsförbättring. De kvalitativa resultaten pekade på att kategorisering och summeringstexter är föredragna features i ett sökgränssnitt i smarttelefonen.

No description available.

I och med lanseringen av nya och mobila plattformar, såsom smarttelefoner och surfplattor, uppstår svårigheter med att anpassa webbsidor för samtliga typer av enheter. Tidigare har mobila applikationer (appar) och mobila sidor använts för att överkomma dessa problem. Responsive Web Design (RWD) är en ung designprincip som uppkom 2010 och har anammats av många webbutvecklare. Designprincipen medför att en webbsidas presentation förändras beroende på skärmstorleken som används för att visa sidan. I en studie har fem företag intervjuats för att få deras tankar och åsikter om RWD i jämförelse med utveckling av mobila sidor och appar. Detta för att besvara huruvida RWD kan ersätta denna plattformsspecifika utveckling. Majoriteten av företagen har helt gått över till att utveckla responsiva webbsidor istället för andra mobilanpassningar men appar utvecklas fortfarande. Skiftet från mobila sidor beror främst på att denna typ av lösning kräver dubbelt arbete med innehållet då olika innehåll visas på olika enheter. Med RWD används istället samma innehåll över samtliga olika skärmtyper. Undersökningen visar på att RWD kan ersätta plattformsspecfik utveckling av informationssidor och e-tjänster. Däremot kommer det inte kunna ersätta appar då dessa i grunden fyller olika syften. Vid större krav på funktionalitet är dessvärre RWD inte alltid lämpligt att använda.