3 ms·

> There is no better way to build a mobile app than a native app. There is, if the only tangible alternative to building a native app is not building a mobile

> There is no better way to build a mobile app than a native app. There is, if the only tangible alternative to building a native app is not building a mobile app at all. Every application deals with some amount of sluggishness. Performance is not a mobile app only problem, it's not a new thing and it's not entirely clear, when it's going to be a big problem and when people will be okay with it. With all the strides being made, the future is almost certainly not going to be 3 code bases for 90% of simple CRUD apps, because while the problem of maintaining a lot of code is not getting better for developers, the js glue layer so many people long for most certainly is, and rapidly.

robenkleene 4y ago
> Every application deals with some amount of sluggishness. Performance is not a mobile app only problem, it's not a new thing and it's not entirely clear, when it's going to be a big problem and when people will be okay with it. So we're just throwing our hands up now and saying it's inevitable that a a notes app is just going to be slow? (In 2023!) We are lost. "Thou hast strayed far from the path of the Avatar. Seek now to renew a life of Virtue, lest thy soul pass finally beyond my reach!"
- jstummbillig 4y ago
  No. We just need the sensible solutions to get better. One would be to stop the Apple/Google hostage situation, improve pwa performance and make web apps first class citizens on Mobile (the web apis to make this happen already we exist). Another one is a better translation layer. Right now the second option seems to be winning out. Asking devs to suck it up and continue down the triple code base insanity for mostly just reasonable feature parity is not one.
  - isodev 4y ago
    PWAs are more of a symptom than a solution. It's been decades, and we are yet to see solid, popular PWAs that offer the cost, performance, efficiency, and accessibility needed to offer transformative change. PWAs also don't solve the root problem of having to deal with different platforms. Many choose to imagine that Chrome is the only browser that matters, but that's far from true. Like native apps, PWAs are hostages to the platform they run on – browser makers.

robenkleene 4y ago

> Every application deals with some amount of sluggishness. Performance is not a mobile app only problem, it's not a new thing and it's not entirely clear, when it's going to be a big problem and when people will be okay with it. So we're just throwing our hands up now and saying it's inevitable that a a notes app is just going to be slow? (In 2023!) We are lost. "Thou hast strayed far from the path of the Avatar. Seek now to renew a life of Virtue, lest thy soul pass finally beyond my reach!"

jstummbillig 4y ago
No. We just need the sensible solutions to get better. One would be to stop the Apple/Google hostage situation, improve pwa performance and make web apps first class citizens on Mobile (the web apis to make this happen already we exist). Another one is a better translation layer. Right now the second option seems to be winning out. Asking devs to suck it up and continue down the triple code base insanity for mostly just reasonable feature parity is not one.
- isodev 4y ago
  PWAs are more of a symptom than a solution. It's been decades, and we are yet to see solid, popular PWAs that offer the cost, performance, efficiency, and accessibility needed to offer transformative change. PWAs also don't solve the root problem of having to deal with different platforms. Many choose to imagine that Chrome is the only browser that matters, but that's far from true. Like native apps, PWAs are hostages to the platform they run on – browser makers.