If you're writing five apps, you're doing it wrong. A huge amount of probably any app can be contained in a common blob of business logic and wiring, with some native presentation on top. Yes, I oversimplify, but folks have been doing exactly that for decades. More work? Yup, even with a common engine it's more work than firing up Electron. That's where "do we even give a shit about what we're shipping?" comes in. If there's no pride in the finished product, well, Electron isn't going to save your product, either.
Especially since all the critical "business logic" in this case that will be shared is likely to be the backend store front APIs and what not. It's the platform things which will end up being radically different.
> A huge amount of probably any app can be contained in a common blob of business logic and wiring, with some native presentation on top.
I keep seeing people claim this, yet most UI software I see really doesn't do anything that complicated. It's some basic database CRUD stuff and some basic algorithms, and then all the actual effort lies in making the UI feel good.
> Yeah the problem is having to write 5 apps, not the inconsistency.
Isn’t that what abstraction and interface is about? You can write the common business logic and presentation concerns, and then share it across each native implementation.
That is what web wrapping is in truth, but it’s just inneficient because of the huge surface area of web technologies.
Aesthetics, usability, and technical flavor are different axes and feel right is a subjective point. And based on anecdata, usability is what actual users want. Web wrapping is mostly an exclusive focus on aesthetics. With native frameworks, you often get very close to "feel right" without much effort.
If you're writing five apps, you're doing it wrong. A huge amount of probably any app can be contained in a common blob of business logic and wiring, with some native presentation on top. Yes, I oversimplify, but folks have been doing exactly that for decades. More work? Yup, even with a common engine it's more work than firing up Electron. That's where "do we even give a shit about what we're shipping?" comes in. If there's no pride in the finished product, well, Electron isn't going to save your product, either.
IME, the UI library idiosyncrasies are the pieces that take the longest to get right. Common business logic is super simple by comparison.
Especially since all the critical "business logic" in this case that will be shared is likely to be the backend store front APIs and what not. It's the platform things which will end up being radically different.
> A huge amount of probably any app can be contained in a common blob of business logic and wiring, with some native presentation on top.
I keep seeing people claim this, yet most UI software I see really doesn't do anything that complicated. It's some basic database CRUD stuff and some basic algorithms, and then all the actual effort lies in making the UI feel good.
> Yeah the problem is having to write 5 apps, not the inconsistency.
Isn’t that what abstraction and interface is about? You can write the common business logic and presentation concerns, and then share it across each native implementation.
That is what web wrapping is in truth, but it’s just inneficient because of the huge surface area of web technologies.
For a whole lot of apps, almost all of the difficult stuff is in making the UI feel right.
Aesthetics, usability, and technical flavor are different axes and feel right is a subjective point. And based on anecdata, usability is what actual users want. Web wrapping is mostly an exclusive focus on aesthetics. With native frameworks, you often get very close to "feel right" without much effort.
1 reply →