search

google / WebFundamentals

Former git repo for WebFundamentals on developers.google.com
Apache License 2.0
13.85k stars 2.57k forks source link

Migrating your existing app to be a PWA (Guide) #3469

Open addyosmani opened 8 years ago

addyosmani commented 8 years ago

Different ways to build a PWA in a progressively enhanced way (i.e not from scratch). The ask was for a comprehensive guide if we can pull that off.

One previous exploration: https://codelabs.developers.google.com/codelabs/migrate-to-progressive-web-apps/index.html?index=..%2F..%2Findex#0

addyosmani commented 8 years ago

Assigning to @jakearchibald initially

cwilso commented 8 years ago

@addyosmani You didn't actually assign jake to this.

addyosmani commented 8 years ago

@cwilso I can't. He's not part of the org. I invited him a few days ago :/

jakearchibald commented 8 years ago

I'm really struggling to get started with this. I can't see how we can write a comprehensive guide that covers:

In many cases, half of one of the points above is its own article.

I'm going to switch to writing a "creating an offline fallback page" with an existing site in mind. I'll throw in manifest too. I'll make reference to the other requirements, and end with a "next steps" thing that points out to push messaging, background sync, full offline-first etc etc.

jakearchibald commented 8 years ago

If anyone disagrees with the above, let me know what the article should actually cover.

PaulKinlan commented 8 years ago

We have core sections that already cover Responsive Design, HTTPS, Push and Manifest (iirc) so we can quite easily just delegate to each of these.

I think the plan for offline fallback page as the first step in a longer strategy (and also as something we can complete this week) makes lot of sense.

@petele @addyosmani where do you envisage this living?

petele commented 8 years ago

I'd like to see this as an update to the existing code lab. As Jake points out, it's too hard to do as a comprehensive guide. It's too broad, it's hard to update and can't get into enough detail to be really helpful for developers.

addyosmani commented 8 years ago

I'd like to see this as an update to the existing code lab. As Jake points out, it's too hard to do as a comprehensive guide. It's too broad, it's hard to update and can't get into enough detail to be really helpful for developers.

👍

Meggin commented 8 years ago

Assuming this is obvious, but you never know... there is a codelab-- so this one can just get updated, right?

https://codelabs.developers.google.com/codelabs/migrate-to-progressive-web-apps/index.html

And then the Instant & Offline docs can just link to it in passing.

Meggin

On Wed, Sep 28, 2016 at 4:10 PM, Addy Osmani notifications@github.com wrote:

I'd like to see this as an update to the existing code lab. As Jake points out, it's too hard to do as a comprehensive guide. It's too broad, it's hard to update and can't get into enough detail to be really helpful for developers.

👍

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/WebFundamentals/issues/3469#issuecomment-250327931, or mute the thread https://github.com/notifications/unsubscribe-auth/ABfU4Tury-S4ZZX0KBeF7dJF9Ky75CSjks5quvPhgaJpZM4KEfCg .

petele commented 8 years ago

Yep - that's the one I'd like to see updated.