For a long time I’ve been thinking about what the future of the web looks like when we go past what we know as the traditional web browser. I called this The Headless Web and I wanted to answer was “What if everything was powered by ‘The Web’, but you never saw a browser?”. Specifically I believe that if you have access to a full browser, but no visible to “chrome” then there is a huge opportunity for a new set of services.
Using the browser as a service is an incredible opportunity. It allows us to take the declarative…
Michael Mahemoff taught me a lot about the possibilities of the web. Prior to working with Mike I built on the web and I understood the benefits such as linkability and discovery, but I never really had a full picture of what would be possible.
One thing that Mike said was “the Web is my API”, where he talked about the being able to expose your site and your data in a page via microformats and other structured data and being able to access it directly from another another browser context, using a simple XMLHttpRequest and the CORS API:
I never got over the death of Web Intents. I always felt that there is still a serious problem on the web, we build silos that lock the user into one web site and we don’t connect our apps together to build richer experiences. We have links that allow us to navigate to another site, but we don’t connect our apps to functionality that we can use in our sites. …
As the capabilities of the Web become more aligned with what was once the domain of native experiences there are an increasing number of times where a developer will want to reduce the confusion for their users who have both the web and native apps installed.
Take notifications for example, introduced in Chrome 42; they allow developers to easily re-engage with users who opt to receive messages. But what if the user also has their native app installed? There was no way for you as the developer to know if your user has your app installed on their current device…
This might seem a little odd, but I would love feedback from the web development community about how you see the web and how you see my Web and Chrome Developer Relations team working.
What is below is almost straight from a doc I was writing that describes our high level goals as a team. My worry is that it could be quite hyperbolic, but it is something I would like to see all web developer relations team be held to in the long term.
This isn’t set in stone but I would like to start a discussion around this…
I like Progressive Web Apps. I like the model it offers for how you build good, solid, reliable web sites and apps. I like the principle platform API — service worker — that enables the PWA model to work.
One of the traps that we have fallen into is “App Shell”. The App Shell model says that your site should present a complete shell of your application (so that the experience something even when you are offline) and you then control how and when to pull in content.
By Pete LePage
Note: Want the full list of changes? Check out the Chromium source repository change list
Let’s dive in and see what’s new for developers in Chrome 58!
The structure of your site’s database has large performance impacts, and can be difficult to change. IndexedDB 2.0 changes that.
Chrome first introduced the “Add to Home screen” banners in Chrome 51. This was a big step for the web as it provided users the ability to easily keep a favorite site on their Home screen, much like native apps. We’ve heard from developers like Alibaba that users re-engage 4 times more often with their site added to Home screen. We’ve also seen that tuning the heuristics for add to Home screen to prompt sooner yields to 48% more installs.
We are happy to share that the team has worked on an improved add to Home screen experience that makes…
Last year just before the Chrome Dev Summit, Miguel Casas came up to me and showed me something that blew my mind: Face Detection in the browser using the Shape Detection API. Shortly after that Barcode Detection was added that allowed me to update my QR Code scanner so that I no longer had to include a massive (albeit awesome) port of a QR scanning library.
The Shape Detection API is still in development, and neither the FaceDetection nor the Barcode Detection API’s are available outside experimentations (you need to enable “Experimental Web Platform features” in chrome://flags) but it is…
Within the last 6 months, it felt like a good time to get on board properly with Web Components so I’ve been toying around with bits and pieces. I’ve been thinking about the ecosystem as a whole and I’ve also recently been creating a few elements.
One thing that is really unclear to me is that there is no defined best practice for how to include styles and templates (HTML) with your custom element which means as a consumer of Custom elements you are at the mercy of what the component developer thinks is best.
Looking at early guidance, there…
Lead for Chrome and Web Developer Relations @ Google. Progressive Web Apps. Launched Web Fundamentals with Web Starter Kit. Mobile BadAss. Mr Web Intents.