Earlier quoted context omitted.
I can’t disagree more. I find gmail to be a perfect example of why web apps are playing to the lowest common denominator and result in poor user experiences everywhere. Just my opinion though, I realise most people love it.
What feature of native apps do you wish web-GMail had?
Apple’s refusal to support Progressive Web Apps is a detriment to the web
341–350 of 451 posts
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#342Earlier quoted context omitted.
I hate threaded conversations, so that isn't something I even value.
Even if you personally dislike it, I think you can agree that it's one of the UX choices that made it storm over the alternatives at the time. Not all our individual tastes align with what's most popular, obviously.
I still manage my own email servers.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#343I think a lot of commenters here are missing the point and getting distracted by push notifications (who wants a website spamming them with notifications?) and loading screens (hardly a feature). Apple supporting PWA (Progressive Web Apps) is hugely important because it enables a future where web apps can natively support browser, Mac/Windows/Linux desktop, and mobile iPhone/Android/Windows native mobile with a singl…
But as an iOS user I expect you to use the technology stack provided by my preferred operating system. I don't want to use your app if you're targeting a lowest-common-denominator feature set. When I change my preferred text size through accessibility settings, good native apps respond correctly. If I need voice over support, the operating system knows how to read the view hierarchy to me in a logical way. When drag-…
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#344I think a lot of commenters here are missing the point and getting distracted by push notifications (who wants a website spamming them with notifications?) and loading screens (hardly a feature). Apple supporting PWA (Progressive Web Apps) is hugely important because it enables a future where web apps can natively support browser, Mac/Windows/Linux desktop, and mobile iPhone/Android/Windows native mobile with a singl…
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#345Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#346I think a lot of commenters here are missing the point and getting distracted by push notifications (who wants a website spamming them with notifications?) and loading screens (hardly a feature). Apple supporting PWA (Progressive Web Apps) is hugely important because it enables a future where web apps can natively support browser, Mac/Windows/Linux desktop, and mobile iPhone/Android/Windows native mobile with a singl…
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#347Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#348Earlier quoted context omitted.
>But as an iOS user I expect you to use the technology stack provided by my preferred operating system. I don't want to use your app if you're targeting a lowest-common-denominator feature set. I would wager that the average quality of an iOS app written by someone like OP that "has a web experience and _has_ to learn iOS just to work on that platform" will probably be lower than if that person (with web experience)…
> iOS app written by someone like OP That's a business choice that they made, and will suffer for. If a developer and business choose to half-ass the native iOS application, there's no reason to believe it would behave any better on iOS when written as a webapp. > the tools they need to write the best product they can The best product that can be made will never be made with cross-platform tooling. It will always be…
Java on a phone is nothing new, but the Java for Symbian you'd write probably wouldn't work very well on a desktop. VC++ for Windows Mobile apps wouldn't work well on a desktop either. The web is the lowest common target, even though it's quite a high level to target. We still run into plenty of HCI issues (why is there a big fat + button in the lower-right on my laptop in GDocs instead of "New" or File -> New action? Because Material is mobile-first and applied thoughtlessly to non-touch experiences), but if you play your cards right, it's now possible to have a codebase, and truly the same app, running on whatever OS and architecture the user has, without specifically building and packaging for 30 different target combinations.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#349I hate using web apps. On desktop, mobile, wherever. The author's list of things they want supported by Mobile Safari is just aggravating: > Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them: > > Create an app loading screen > Use push notifications > Add offline support > Create an initial app UI to load instantly > Prompt installation to the home screen through b…
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#350Earlier quoted context omitted.
Apple supporting PWA (Progressive Web Apps) is hugely important because it enables a future where web apps can natively support browser, Mac/Windows/Linux desktop, and mobile iPhone/Android/Windows native mobile with a single codebase of open technologies. Why after over 30 years of experiencing cross platform "write once run anywhere* technologies do developers still think that's the best user experience? Yes it mak…
GMail was (and maybe keeps being) a much better user experience than native email clients for desktop PCs.