Re: [w3ctag/design-reviews] App history API (#605)

Thanks for continuing to take a look!

> one thing that came up in the f2f today (and apologies in advance for bike-shedding): we think "App History" is confusing because it implies this is about the history of apps on a device or similar. It feels like this has scope across the web. We don't have a good alternative suggestion... WebAppHistory?

Very interesting! I hadn't heard this particular name feedback before, but it makes sense. We have our general bikeshedding issue at https://github.com/WICG/app-history/issues/83 . See also some of the discussion on the "app" prefix from a web developer perspective at https://github.com/WICG/app-history/issues/83#issuecomment-805951408 .

> We're concerned about adding a new API that has to do with history which developers will find confusing on top of the existing history API. At the same time it's clear that it's meeting a user need. The example of XHR and Fetch came up in our discussion. In that case, it was clear what we were asking developers to do - migrate to Fetch. Can we do the same with this API? 

Yeah, the plan is indeed that we'd like developers and apps to migrate to this new API, leaving `window.history` (and perhaps even `window.location`??) in the dust. The exact details are under discussion in https://github.com/WICG/app-history/issues/67 .

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/605#issuecomment-838954742