Photo by Scott Webb from Pexels

This post intends to tell the story of having the huge opportunity to develop a new frontend, an AMP-compatible website, for a big and global company.


Early this year, the retail company where I work (https://www.garbarino.com) decided to create a PWA.

It was a great moment for a web technologies fan like me, being part of it. Argentina has not reliable mobile connections, our clients might not want to install the native app and, fortunately, 80% of our mobile traffic is from chrome. So, let’s do it! 💪

The key objective

To improve the experience on mobile.

Project setup

Before writing any line of code, we had to define some important aspects.

This was the perfect time to face an expected redesign on our mobile user experience.

We made ourselves some…


This guide might be a bit out of date. Now, App Engine supports Node on its standard environment.

Take a look here: https://cloud.google.com/appengine/docs/nodejs/ and choose the way that fits better to you and your project. If you prefer the flexible environment, this guide could still be useful for you.

Surely anyone who has developed a project to run on App Engine (Google’s PaaS) could have found a situation like this:

  • The platform is very interesting.
  • The services and libraries provided solve many common problems.
  • The configuration required is minimal, Google does the rest.
  • The way in which it scales is…

Leonardo Pittelli

Software Engineer. Fan of web technologies. Google Developer Expert for Web and Cloud. FullStack JS Dev / Chapter Lead Web @olxtecharg. Prev: PWA TL @garbarino

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store