zlacker

>>iBelie+(OP)
My primary concern with this is that different applications are inherently optimized for the platform on which they were originally designed. There are some applications that have a very dense UI because there's simply alot of functionality that the program handles (think of a video editor, an IDE, etc). Trying to slim down those applications to make them reactive so that they will scale onto a phone or tablet just seems silly, and I fear that in the name of making "everything work everywhere", we're going to compromise a bunch of apps that worked beautifully on one platform in favor of making them work adequately on several platforms.

I mean, if someone said, "I've successfully ported Vim to Android!", my first thought would be, "Why in god's name would I want to run vim on my phone?"*

* Ruling out, of course, someone plugging their phone into external KVM.

>>Admira+K7
Exactly what you're describing already happened when the netbook fad took hold some years ago. It's crazy obvious on Gnome but KDE apps suffered too, and the defaults to this day are still shit (optimized for form factors 2% of people use).

I feel like the solution is not necessarily to make one app do it all, but to embrace something more akin to a client-server architecture - one "app" with multiple UIs talking over the same API to the same backend logic.

>>peller+mr
This “client-server architecture” sounds eerily similar to plain old MVC/MVP/MVVM...

Decoupling the UI from the business logic is not exactly a new concept.

>>aaaaaa+NJ
Agreed, and that's kind of the point - this shouldn't be a problem to begin with, aside from the fact that "everybody" prefers to write their own shit from scratch :)