Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Google AMP and what it can do for mobile applications in terms of rendering speed and user-experience
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
2019 (English)Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
Abstract [en]

On today’s web, a web page needs to load fast and have a great user experiencein order to be successful. The faster the better. A server side rendered webpage can have a prominent initial load speed while a client side rendered webpage will have a great interactive user experience. When combining the two,some users with a bad internet connection or a slow device could receive a pooruser experience. A new technology called Amplified Mobile Pages (AMP) wascreated by Google to help combat this issue.The authors of this report gives an answer to if Google AMP could maintain theuser experience while still contributing with a fast initial load speed for applica-tions. To do this, we conducted an experiment through creating a Google AMPapplication and compared it to another application using a different renderingengine called Pug. We have also measured the metrics: page load time, speedindex and application size between the two applications. To fully understandthe AMP format, the authors conducted a literature study, to further strengthentheir findings.Google AMP is a great technology but it can still grow to become better. Theformat could increase the speed of a website, however the same result could beachieved without AMP if focus was set on writing a fast application. From theexperiment, the authors concluded that Google AMP takes a great time to learnbecause of its own version of JavaScript through modules. The format also hasa different structure than standard HTML. From the tests, a smaller applica-tion does not favor the implementation of AMP. We did however derive fromthe experiment and the literature study that bigger applications could benefitfrom the perks of AMP and could therefor be a potential choice for old and newapplications.

Place, publisher, year, edition, pages
2019. , p. 48
Keywords [en]
Google AMP, User Experience, Performance, Mobile Web Pages, Speed
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-17952OAI: oai:DiVA.org:bth-17952DiVA, id: diva2:1328066
Subject / course
PA1445 Kandidatkurs i Programvaruteknik
Educational program
PAGWE Web Programming
Supervisors
Examiners
Available from: 2019-06-24 Created: 2019-06-20 Last updated: 2019-06-24Bibliographically approved

Open Access in DiVA

Google AMP and what it can do for mobile applications in terms of rendering speed and user-experience(861 kB)100 downloads
File information
File name FULLTEXT02.pdfFile size 861 kBChecksum SHA-512
cbe48798129cc56e6182e6e47c194ff3971002a34fbc9ecc054bc4084b4e48b047ec0c80dec2ccc97bd4bb1c997c720da8c786683327657e930caa8a0d313bc0
Type fulltextMimetype application/pdf

By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 100 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 218 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf