111–120 of 163 posts
What's the alternative? Certainly multi platform native only makes sense at a certain scale. Your question might be too light on details to provide much advice.
Earlier quoted context omitted.
> But some of us also want support tech that fulfills the goals of the open web. You don't seem to care about that, but others do. Telling everyone its basically a lost cause is a silly and pointless endeavor, because PWAs are the long game, and you're playing the short game. Get off the cross, we could use the wood. Spare me. I love the web, in fact all my “apps” are built with web tech and I offer them all as websi…
>If you actually care so much about PWAs then stop writing PWAs that your users hate using and go be a full time advocate for that instead. I do care about PWAs, and so I am advocating, right now. I don't know why you come across as so angry about people who advocate for PWAs. Pushing companies to adhere to open web standards is a good thing, otherwise we'd still be stuck in IE6 world.
“Preaching to the choir” comes to mind.
I'll give you a hard-earned tip: expect to fight Apple every step of the way. They will randomly erase all local data (cookies, localstorage, push subscription tokens, etc) in your PWA without warning. They say they don't do this, but I have the receipts. They want PWAs to suffer, and you will go insane trying to make workarounds on iPhone.
Are you saying the Safari browser on iOS intentionally cripples web applications by randomly erasing / deleting browser data (cookies, localStorage, etc)? And this happens on purpose because apple wants to boost App Store Apps usage? If there is evidence of the veracity of this claim, this topic deserves a whole lot more attention. Especially considering Apple's stance on 3rd party mobile web browser engines - Apple…
I would absolutely make this claim.
This isn't even a PWA thing. We had a really simple series of boring web forms that suffered from this. The first iteration of this had the server swap an initial tokenized link for a cookie when clicked.
After some feedback from our customers, we discovered that iOS users were having a lot of trouble getting all the way through the desired workflow. We were able to replicate this on our iOS devices but it seemed completely arbitrary.
After abandoning cookies in favor of maintaining a tokenized URL, we found we were getting 100% success rate for iOS end users.
My theory is there is a malicious bit of code in iOS Safari that is applying some insane cookie policy over "unpopular" domains.
https://FreeSolitaire.win is a successful PWA of mine. It’s a Klondike Solitaire game. It used to bring ~$500/mo of advertising revenue, but that’s significantly down these days: I refuse to have a cookie/consent banner, so I refuse customized ads (in the UE, in some US states now, &c.) Players do add it to homescreen. There is a non-intrusive button prompting them to do so, at the end of a game. People like to be ab…
Why does it let you sort through the card deck one-by-one? Ime mkst solitaire offers the top of a set of three. Maybe it's just a different style of solitaire? This one seems too easy, though. Well done app, regardless - cheers! :)
https://FreeSolitaire.win is a successful PWA of mine. It’s a Klondike Solitaire game. It used to bring ~$500/mo of advertising revenue, but that’s significantly down these days: I refuse to have a cookie/consent banner, so I refuse customized ads (in the UE, in some US states now, &c.) Players do add it to homescreen. There is a non-intrusive button prompting them to do so, at the end of a game. People like to be ab…
Nice and clean! How did you get it off the ground and gather first users?
Word of mouth, mainly. Posted it on Reddit back then, things like that. It grew organically from that. And, although it’s far from being on top results on SERP (search engine result pages), some people do find it that way.
Also: because it’s so lightweight, it got included some years ago in the Moya app (https://play.google.com/store/apps/details?id=nu.bi.moya), a popular messaging app in South Africa that is “data-free” for users (it does reverse-billing). Now half the players are South Africans!
Flipkart.com and housing.com and few good examples
Earlier quoted context omitted.
>If you actually care so much about PWAs then stop writing PWAs that your users hate using and go be a full time advocate for that instead. I do care about PWAs, and so I am advocating, right now. I don't know why you come across as so angry about people who advocate for PWAs. Pushing companies to adhere to open web standards is a good thing, otherwise we'd still be stuck in IE6 world.
It doesn’t count as advocating is your audience is only people who (in general) agree with you. I don’t think anyone on hackernews wants PWAs to be a worse experience, but they are . If you want to make a difference, you’re not gonna make it here. “Preaching to the choir” comes to mind.
I'm replying to the people who disagree with me here, and there are several. The readers who are on the fence can make up their own mind. Your discouragement is not necessary or useful.
Earlier quoted context omitted.
Great point. The fact that they don’t backup to the cloud PWA data makes it a non-starter for any app that wants a local only experience. It’s trash.
I am not sure that I would be happy with a 'local only' experience actually backing up data to the cloud.
Earlier quoted context omitted.
Are you saying the Safari browser on iOS intentionally cripples web applications by randomly erasing / deleting browser data (cookies, localStorage, etc)? And this happens on purpose because apple wants to boost App Store Apps usage? If there is evidence of the veracity of this claim, this topic deserves a whole lot more attention. Especially considering Apple's stance on 3rd party mobile web browser engines - Apple…
> Are you saying the Safari browser on iOS intentionally cripples web applications by randomly erasing / deleting browser data (cookies, localStorage, etc)? I would absolutely make this claim. This isn't even a PWA thing. We had a really simple series of boring web forms that suffered from this. The first iteration of this had the server swap an initial tokenized link for a cookie when clicked. After some feedback fr…