Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
Thanks David for this article, especially for the polls and background-infos.
Here's my story with PWAs: For a loooong time I heard "PWA" come up in articles and blog posts, but I felt it was too unimportant to have a look at it, let alone build one myself. I only knew what the acronym means, and nothing more. PWAs occasionally crossed my path on the internet, but I still didn't bother. Then, a few days ago, I added dev.to to my start screen - without even knowing it was a PWA - and was wondering why it took Chrome so long, and when I first opened it I was a bit confused. No address bar, no menu, nothing. And it felt "just like a mobile app". Quite nice, actually. It's a bit magical, and I bet that very few people, and literally NO non-tech people, know about the concept of PWAs. A few days later I stumbled upon your post, just when the dev.to PWA was still pretty new to me, which was a funny coincidence. I thought about the recent trouble of Hey (that new email thing from the basecamp team) with the Apple App Store, and how my colleague, who manages our apps on App Store and Play Store, hates Apple's App Store for it's random technical and policy-changing issues that cost him literally a few hours per week to solve. PWAs seem like a good thing in this context, liberating app distribution, it feels like a good match to other de-centralizing efforts.
I'm pitching a solution next monday which, when being sponsored, might be a good fit for a PWA, but I'd still be very skeptical about building one. [App/Play] Store are a good marketing instrument which makes your App and your brand visible to a wider audience. All in all, I think that PWAs still have a long way to go, if they even ever will go mainstream. The decentralized, independent nature is very appealing, though.
Thank you for sharing this story, indeed a funny coincidence and it was a nice read 😉
Agree with you, in terms of business, there are still some uncertainty about PWAs. Also to my high, a certain lack of statistics to know if a wider (non tech) audience accept and use these. Probably few I am guessing but I might be surprised.
Regarding the solution you are pitching next week, note that framework like Ionic, which I use often, are making possible to write apps with the same code base for iOS, Android and PWA. Depending of the features you are in need, there are possibilities to already include PWA in a plan where the apps are also ship in stores.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks David for this article, especially for the polls and background-infos.
Here's my story with PWAs: For a loooong time I heard "PWA" come up in articles and blog posts, but I felt it was too unimportant to have a look at it, let alone build one myself. I only knew what the acronym means, and nothing more. PWAs occasionally crossed my path on the internet, but I still didn't bother. Then, a few days ago, I added dev.to to my start screen - without even knowing it was a PWA - and was wondering why it took Chrome so long, and when I first opened it I was a bit confused. No address bar, no menu, nothing. And it felt "just like a mobile app". Quite nice, actually. It's a bit magical, and I bet that very few people, and literally NO non-tech people, know about the concept of PWAs. A few days later I stumbled upon your post, just when the dev.to PWA was still pretty new to me, which was a funny coincidence. I thought about the recent trouble of Hey (that new email thing from the basecamp team) with the Apple App Store, and how my colleague, who manages our apps on App Store and Play Store, hates Apple's App Store for it's random technical and policy-changing issues that cost him literally a few hours per week to solve. PWAs seem like a good thing in this context, liberating app distribution, it feels like a good match to other de-centralizing efforts.
I'm pitching a solution next monday which, when being sponsored, might be a good fit for a PWA, but I'd still be very skeptical about building one. [App/Play] Store are a good marketing instrument which makes your App and your brand visible to a wider audience. All in all, I think that PWAs still have a long way to go, if they even ever will go mainstream. The decentralized, independent nature is very appealing, though.
Thank you for sharing this story, indeed a funny coincidence and it was a nice read 😉
Agree with you, in terms of business, there are still some uncertainty about PWAs. Also to my high, a certain lack of statistics to know if a wider (non tech) audience accept and use these. Probably few I am guessing but I might be surprised.
Regarding the solution you are pitching next week, note that framework like Ionic, which I use often, are making possible to write apps with the same code base for iOS, Android and PWA. Depending of the features you are in need, there are possibilities to already include PWA in a plan where the apps are also ship in stores.