Because it’s too complex and not worth the effort. Most users will not care about or perceive the benefit. If they delegate that responsibility to Google via Electron, they can focus on features/bug fixes that move the needle.
replyWhat effort ? I’ve started seeing this attitude more and more. We had a thing that took a week to do before. Now it takes a morning. So we refuse to spend half a day polishing it because it’s too annoying.
replyOnce the initial port is done, keeping platforms in sync is fast. Not to mention that a harness that would automate this would be valuable.
I run codex on an old rpi, it eats 190M of ram for what essentially is a telnet client.
You're mistaken if you think it has ever taken a week to port (and support) an application to native primitives.
replyThis isnt how a company which has "solved programming" would act.
replyEspecially since users do prefer a native experience and having their RAM conserved.
I have a question about web to iOS native. How do you distribute that app? I’m assuming you’re paying $99 yearly to distribute through the App Store? Is this app meant just for you or for anyone to find?
replyReason I’m asking is because I’d like to make native iOS apps just for myself rather than progressive web apps. But I haven’t understood the best way to distribute.
If just for yourself, get an Apple Dev account and use TestFlight
replyDo I need to upload a new build of the app every 90 days? I’d prefer the app to just work forever without thinking about it.
reply