These are part of the google computing engine cloud service and are extremely fast for AI-based computing
Visual Positioning Service, Google Lens, and other Visual/AI Combinations
Google’s Visual Positioning Service uses Augmented Reality to find key visual points for indoor navigation withiut GPS or beacons.
Google Lens is also able to pull objects out of photos and create a data presentation. For instance, a photo of the Chicago cityscape could be analyzed and then provide information about the individual buildings.
Lighthouse is being integrated directly into dev tools
Firebase now gives a real time analytics. Cloud functions for Firebase sounds like Akamai for small node functions, like resizing images. But being able to handle these tasks in a global, cached environment.
Google IO: state of the mobile web
Chrome’s mission: move the web platform forward
scroll anchoring: page jumps after content loads after page renders, such as a banner ad. This locks the screen, even when content loads at the top. Scroll anchoring can reduce 3 page jumps per load on average.
AMP: Accelerated Mobile Pages. improve mobile experience.
On average, AMP pages load in less than a second and use 10x less data
LinkedIN found people were 10% more likely to read an article when it is AMP .
amp-bind: merchants can build e-commerce experiences
Progressive web apps: app focused experiences, reliable, fast, engaging.
Twitter Lite is a more accessible, faster and more affordable way for people to use Twitter when they are on slow mobile networks, have expensive data plans and with limited storage on their mobile device.
PWAs can be added to the home screen. Developers can soon control the home page button prompt. They can be displayed in app launcher, android settings, android intents, notifications, and launch as a full-screen immersive view
123B in US alone
paymentRequest – simple web payments within Chrome
paymentRequest can now use more forms of payment. paypal, alipay, samsung pay… could this integrate quickbooks payments?
India’s largest ride sharing app. They are using PWA. over 1m daily rides. 110 cities and 600k drivers. They needed to work with customers that use low cost phones, minimal data plans, and bad connections to reach the entire customer base.
Off line and caching provides faster performance with low data loads. They used polymer for fast web components, Shadow DOM, and HTML import.
They rely heavily on cache, but also have an initial load of 1.3 seconds.
They strategically load components to only get critical elements first.
They are using workbox, they cache these elements for repeated use.
Now, they are only requesting new data, such as transaction information.
They have a 100 score in lighthouse
20% of their PWA bookings come from users that previously uninstalled their Android app
AMP to PWA
<amp-install-serviceworker>. This takes an AMP page and allows it to install a service worker so a user shifts to a PWA when they click. This gives the fast initial page load of an AMP page and prepares the browser to make the second page load just as fast.
Let’s say someone shares a PWA page with a friend. We’d want the friend to have a fast page load, but if they go to a PWA page as the first experience, they won’t get the acceleration via the service worker. So we could do some detection at the page load to see if the service worker is available, if not, move to the AMP experience of that page.
I just found out about the Dive Into HTML5 tutorial. It’s downright amazing. I wish all specs were so carefully described. Don’t miss the first chapter on the history of standards creation. It gives you a good understanding of why the HTML standards are quirky and why HTML5 is progressing the way it is.
I especially like the way they test your browser for its ability to handle the various components you are reading about. Take an hour or so to go through this tutorial. It’s the best read you’ll have for the week.
Another good tutorial is The Best HTML5 Slides Ever, but you’ll need to view it in Safari. It doesn’t work well in the standard Firefox and forget about IE.
There’s a lot of information about Yahoo! Boss on the official site: Yahoo! Developer Network. However there is still a need for a more informal portal for quick reviews of BOSS-based mashups, helpful hints, techniques, and upcoming events.
BOSS Hacks is an unofficial Yahoo! BOSS Site that does exactly that. I started it last week as I noticed this site was becoming less about standards based markup and more about how I was working with Yahoo! BOSS.
This site will feature shorter, more succinct blog posts. I’ll save any large posts for the YDN blog. Please feel free to visit the site and send me notes about what you would like to see or any new BOSS-based sites that should be mentioned.