URLs are UI
▻https://www.hanselman.com/blog/URLsAreUI.aspx
“Make it a priority that your website supports shareable URLs.”
URLs are UI
▻https://www.hanselman.com/blog/URLsAreUI.aspx
“Make it a priority that your website supports shareable URLs.”
Les instincts d’hier deviennent les bonnes pratiques de demain. Dommage de devoir en passer par là.
Ce sont de bonnes pratiques depuis déjà longtemps, en fait. Typiquement, le Cool URIs don’t change de Tim Berners Lee en 1998 : ▻https://www.w3.org/Provider/Style/URI
Je suis retombé sur un document synthétique de google à ce sujet
►https://developers.google.com/web/progressive-web-apps
@booz ▻https://seenthis.net/messages/523608
@klaus ▻https://seenthis.net/messages/523013
Dommage qu’ils n’aient pas mis le caractère « linkable » des PWA dans cette page d’intro.
C’est heureusement dans la checklist : ▻https://developers.google.com/web/progressive-web-apps/checklist#each-page-has-a-url
Question qui avait été postée en 2011 sur seenthis (@seenthis) :
« Et sinon, des #applis #smartphone prévues pour #Seenthis ? »
5 ans après, en 2016... est-ce qu’il y a une évolution ?
Concernant la lecture hors-ligne, qui me semble le seul (?) avantage potentiel d’une appli native sur la version web, il y a des choses possible désormais en javascript dans le navigateur, qui peut servir de cache et de base de donnée pour un site web mobile lisible hors-ligne,[edit] avec notifications web, et tâche de fond. Voir #pwa par exemple, et #local_storage et #IndexedDB
Cela me semblerait intéressant de creuser cela pour SPIP dans son ensemble.
Les notifications aussi sont un avantage, la mise à jour en tache de fond....
Les notifications et tâches de fond on l’air possibles également.
►https://developers.google.com/web/progressive-web-apps
Push Notifications
Web push notifications makes it easy to re-engage with users by showing relevant, timely, and contextual notifications, even when the browser is closed.
▻https://w3c.github.io/ServiceWorker/spec/service_worker/index.html
This specification describes a method that enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of web applications while offline.
The core of this system is an event-driven Web Worker, which responds to events dispatched from documents and other sources. A system for managing installation, versions, and upgrades is provided.
The service worker is a generic entry point for event-driven background processing in the Web Platform that is extensible by other specifications.
Si les magiciens de seenthis arrivaient à avoir une lecture hors-ligne, ça serait tellement utile !!!!!!
Le service qui serait LE truc utile pour moi serait de s’intégrer au système de partage sur Android, de manière à ce que, quand je lis un article cool, je puisse le partager sur SeenThis aussi facilement que via Twitter, courrier, SMS, etc.
Web | Google Developers | Progressive Web Applications
►https://developers.google.com/web/progressive-web-apps
▻https://lh3.googleusercontent.com/ztrksWcAyubvXbnAskphQ4hVY2sef4iEIEmxth1HJj6jZkzmB9qYe89YSXfzr
Progressive Web Applications take advantage of new technologies to bring the best of mobile sites and native applications to users. They’re reliable, fast, and engaging.
On nous promet ... tout !
Instant Loading
Service workers allow your apps to load nearly instantly and reliably, no matter what kind of network connection your user is on.
Add to Home Screen
Web app install banners give you the ability to let your users quickly and seamlessly add your web app to their home screen, making it easy to launch and return to your app.
Push Notifications
Web push notifications makes it easy to re-engage with users by showing relevant, timely, and contextual notifications, even when the browser is closed.
Fast
Smooth animations, scrolling, and navigations keep the experience silky smooth.
Secure
HTTPS secures the connection between you and your users, ensuring your users information is protected and isn’t tampered with.
Responsive
Modern users live on phones, tablets and laptops; your apps and websites should do the same. Learn how to structure and code your content to look great on screens of any size.
Est-ce qu’on peut leur faire confiance ou est-ce que c’est encore un monstre qui pompera sur nos réserves avant de se faire la malle ?
▻https://developers.google.com/web/fundamentals/getting-started/your-first-progressive-web-app
Progressive Web Apps are:
Progressive - Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet.
Responsive - Fit any form factor: desktop, mobile, tablet, or whatever is next.
Connectivity independent - Enhanced with service workers to work offline or on low quality networks.
App-like - Feel like an app to the user with app-style interactions and navigation because they’re built on the app shell model.
Fresh - Always up-to-date thanks to the service worker update process.
Safe - Served via HTTPS to prevent snooping and ensure content hasn’t been tampered with.
Discoverable - Are identifiable as “applications” thanks to W3C manifests and service worker registration scope allowing search engines to find them.
Re-engageable - Make re-engagement easy through features like push notifications.
Installable - Allow users to “keep” apps they find most useful on their home screen without the hassle of an app store.
Linkable - Easily share via URL and not require complex installation.