undefined | Better HN

0 pointsevilduck2y ago0 comments

So why would you build a native Android app if PWAs work better? There’s way more web developers than Android developers, and you would avoid the Play Store fees. Sound cheaper to me. What part of iOS is invalidating the value proposition for Android here?

You also didn’t answer what is missing. What is missing? What’s this insurmountable problem that’s solved everywhere else? Why is janky tooling attributable to Apple?

0 comments

beeboobaa2y ago

Try reading my post again, maybe? The tooling is pretty janky because no one does this yet. No point to torture yourself with janky tooling when you only get to target android anyway...

evilduckOP2y ago

Again, not answering a thing but a making up a claim you aren't willing or able to support. How is this supposed web development tooling jankiness attributable to Apple today? Feature detection is a solved problem. What tooling are you even referring to? You aren't even trying to support this with a concrete claim. This is nonsense and you know it.

PWAs are the perfect scapegoat of infinite nebulous whining. The definition of a progressive web app might as well be "whatever Chrome has but Safari doesn't, no matter what year it is or how those features change, and no matter how terrible of an idea they might be even on Chrome".

beeboobaa2y ago

> Proper support on all platforms. No point working on PWAs that have janky tooling (reason: see previous sentence) when they're only going to work decently on Android devices anyway.

If you need it spelled out for you:

* WebUSB

* WebBLE

* WebSerial

* WebGL

* Many more standards Apple refuses to implement because it would let developers break free of their walled garden

Without being able to target apple devices why would I, or anyone, bother using these technologies and invest in their tooling? Just make a native android app with quality tooling that's been around for a decade and be done with it.

evilduckOP2y ago

Right, I wanted you to spell it out because I was expecting you to write that exact sort of nonsense. Your first three examples aren't even web standards they're experimental features in Chrome that not even Firefox supports. The fourth actually is supported by Safari/iOS. What missing standards are stopping you from writing Progressive WEB Apps? Be exact please.

And.... even if you wanted to build a serial-port enabled "Works only in Chrome" PWA today (lol, we both know you're not) there's no tooling jankiness stopping you from doing so, checking for `if ("serial" in navigator) { ... }` requires no tooling at all it's just plain javascript, you'd just choose to show an error message for browsers like Safari and Firefox that don't support it.

I'm not convinced you're even arguing in good faith here. Well, I never was because PWA whiners never are, but you've proven you're not.

j / k navigate · click thread line to collapse

0 comments

beeboobaa2y ago

Try reading my post again, maybe? The tooling is pretty janky because no one does this yet. No point to torture yourself with janky tooling when you only get to target android anyway...

evilduckOP2y ago

beeboobaa2y ago

> Proper support on all platforms. No point working on PWAs that have janky tooling (reason: see previous sentence) when they're only going to work decently on Android devices anyway.

If you need it spelled out for you:

* WebUSB

* WebBLE

* WebSerial

* WebGL

* Many more standards Apple refuses to implement because it would let developers break free of their walled garden

evilduckOP2y ago

I'm not convinced you're even arguing in good faith here. Well, I never was because PWA whiners never are, but you've proven you're not.

j / k navigate · click thread line to collapse