Live data from Hacker News

I built a progressive web app and published it in three app stores

debuggerdotbreak.judahgabriel.com

41–50 of 415 posts

Re: I built a progressive web app and published it in three app stores

#41

From a user perspective, this is why I love iOS. * Barrier to entry. If your project is more than a hobby, you can jump through a couple hoops to reach the iOS userbase. If the difference between $99 and $25 is make-or-break, you're probably trying to publish a hobby/low quality app anyways. There is a reason the Microsoft Store and Google Play are absolutely filled with trash, and this is part of it. * Forcing you t…

totally agree, Apple want quality not quantity, and to protect their users (so they are happy to pay a premium)

Re: I built a progressive web app and published it in three app stores

#42
post #18

We're definitely at the point in history where we have to get out of these app stores . I get it if you're doing a game or something that's fine, stay in the app store. But I don't know how many times I've been extremely frustrated with a website telling me to get their app. * They break my in-browser password store * They introduce extremely complicated "app-only" device links for Oauth * Updating your UI for most a…

One of the ones I hate most is Reddit, which actually has a pretty good web interface. The worst part about their app is I can't search for words in threads.

I'm actually on the other side of this - it's really easy to use their app to browse posts and read comments, where it's a bit more involved using the web interface.

Re: I built a progressive web app and published it in three app stores

#43
post #17

Earlier quoted context omitted.

The dev experience was better with MS's tools, of course. They created PWABuilder, and it *actually generates a Windows Store package (.appx) that can be submitted to the store. No other steps required. Pretty amazing. Google wasn't bad; PWABuilder generated an Android Studio project. You open in Android Studio, build, and it generates the package to be submitted to the store. iOS was sadly the most painful. Not leas…

It’s a lot to do with what you’re used to. As an Apple user bought into their ecosystem and tools, I find developing for their platforms dramatically easier and more straightforward than for other targets. I can basically do Android development with some pain and confusion, but on Windows I’m totally stumped/useless.

Apple needs a better onboarding for new developers and definitely needs to improve XCode to be on part with it's high shipping standards, it also didn't help that a lot of the time the iTunesConnect platform was failing.

I can say however that it is easier to create things of higher quality with the iOS Sdk than it is with the Android sdk, at least it was for me.

Re: I built a progressive web app and published it in three app stores

#45

From a user perspective, this is why I love iOS. * Barrier to entry. If your project is more than a hobby, you can jump through a couple hoops to reach the iOS userbase. If the difference between $99 and $25 is make-or-break, you're probably trying to publish a hobby/low quality app anyways. There is a reason the Microsoft Store and Google Play are absolutely filled with trash, and this is part of it. * Forcing you t…

Controls: It doesn't force me to use native controls. :-) My web app today is still using the free and opened web, and all the goodness that comes with that, for UI and code.

Requiring a Mac: Now you've met one. I built a halfway decent iOS app, and I don't want to spend $7000 on a Mac and its crappy dev tools and frameworks.

I've poured nearly 7 years of work into user experience. I don't need to redo all that for Apple's closed, proprietary platform.

Re: I built a progressive web app and published it in three app stores

#46
post #18

We're definitely at the point in history where we have to get out of these app stores . I get it if you're doing a game or something that's fine, stay in the app store. But I don't know how many times I've been extremely frustrated with a website telling me to get their app. * They break my in-browser password store * They introduce extremely complicated "app-only" device links for Oauth * Updating your UI for most a…

One of the ones I hate most is Reddit, which actually has a pretty good web interface. The worst part about their app is I can't search for words in threads.

I browse the mobile reddit all the time and constant nagging to use the app was a real PITA until I discovered that I don't have to press the link to hide the "browse with the app overlay". You can simply scroll down and it will go away.

Re: I built a progressive web app and published it in three app stores

#47
> From minor things like “iOS Safari won’t let you play audio without first interacting with the page” to major, show-stopping things like, “iOS Safari won’t let you play the next song if your app is in the background or if your screen is off.”

I disagree that these things are purely because Apple wants your $99/year. Maybe that's part of the story, but not all.

I am glad that websites cannot play audio without the user first interacting with the page. I am also glad that websites can't play audio in the background — as a user, I would find it too "buried" behind Safari and I wouldn't appreciate the feeling that a website was running in the background. (Yes I know you can control audio via the Notifications Center and Control Center.)

I appreciate that these permissions are reserved for apps that Apple has vetted, even if this is a pain for developers and they are not a perfect institution, as a user I appreciate that they are trying to maintain quality and encourage good app behavior.

I'm glad your app had to jump through these hurdles to gain the functionality your users wanted. Like you said, it's where the users are they were asking you directly for it. These are higher-level permissions and should not be free for the taking.

Re: I built a progressive web app and published it in three app stores

#48

From a user perspective, this is why I love iOS. * Barrier to entry. If your project is more than a hobby, you can jump through a couple hoops to reach the iOS userbase. If the difference between $99 and $25 is make-or-break, you're probably trying to publish a hobby/low quality app anyways. There is a reason the Microsoft Store and Google Play are absolutely filled with trash, and this is part of it. * Forcing you t…

Most of your arguments are subjective and anecdotal. It’s also “case in point.”

Re: I built a progressive web app and published it in three app stores

#49
post #45

From a user perspective, this is why I love iOS. * Barrier to entry. If your project is more than a hobby, you can jump through a couple hoops to reach the iOS userbase. If the difference between $99 and $25 is make-or-break, you're probably trying to publish a hobby/low quality app anyways. There is a reason the Microsoft Store and Google Play are absolutely filled with trash, and this is part of it. * Forcing you t…

Controls: It doesn't force me to use native controls. :-) My web app today is still using the free and opened web, and all the goodness that comes with that, for UI and code. Requiring a Mac: Now you've met one. I built a halfway decent iOS app, and I don't want to spend $7000 on a Mac and its crappy dev tools and frameworks. I've poured nearly 7 years of work into user experience. I don't need to redo all that for A…

$7000? Your bias is showing. You can buy a Mac for <$1000 and it's perfectly capable of developing most apps.

Re: I built a progressive web app and published it in three app stores

#50

> Mobile platform vendors, like Apple, are totally cool with apps that use your phone to its fullest. Access your location, play background audio, get your GPS coordinates, read all your contacts, play videos or audio without app interaction, read your email, intercept your typing, play more than one thing at a time, use your microphone and camera, access your pictures, and more. Apple’s totally cool with that. Apple…

Partially agree. I understand security concerns; we shouldn't allow random web apps to freely access privileged operations, for example. (Should we allow web apps to ask for permission? That is another question.)

But stopping web apps from working? For example, breaking open standards like "you can't play more than one stream of audio", or "you're not allowed to play audio if your app isn't in the fore"? Nah, that's nasty. It gets worse. iOS's new PWA support actually reloads your whole page - losing all context and execution - every time you bring it to the fore. It kills all execution when putting the app into the background.

This is beyond security; it is actually hostile to users and developers.

Post reply on HN