2 ms·

Are you asserting that HTML/CSS/JS is not at all viable/desirable for making apps, or just not your personal preference? I'd like to know what you feel is best

by rhelmer 13y ago

Are you asserting that HTML/CSS/JS is not at all viable/desirable for making apps, or just not your personal preference? I'd like to know what you feel is best if the latter (and what you feel stops the former - having a standardized high-level platform has advantages!)

programminggeek 13y ago
I've built HTML/CSS/JS mobile apps with phonegap and while it's fun as a developer, the user experience is just not as good as building a proper native app. If you care about user experience, build using what is native to the platform. This is why most web devs don't build web apps using Flash or Java applets anymore. Those aren't native to the platform and don't provide the best possible user experience. HTML/JS as "native" apps to a platform can absolutely work and be awesome, but it really comes down to what "native" on a given platform means. On Android it's Java, on iOS it's Obj-C, on Windows it's C#, on a web browser or Firefox OS it's HTML/JS.
- rhelmer 13y ago
  Thanks, I appreciate the details. There definitely is a "happy path" for each platform, where tools/docs/developer support and getting into the marketplaces and so forth is much simpler and well-understood - things can get dicey when you stray from that.
zanny 13y ago
Using a document markup as your application structural layout, in an environment built around either static links or argument supplemented static links, with the concepts of forward and backward through a chain of pieces of content, I think is a really poor way to design applications. For a better UX and developer experience, that still uses JS, just look at QML. Declarative, application focused, and scriptable in JS. Easy to create one UI that transitions to other layouts, but the elements are first, not the text within them.

2 ms·

Are you asserting that HTML/CSS/JS is not at all viable/desirable for making apps, or just not your personal preference? I'd like to know what you feel is best

by rhelmer 13y ago

programminggeek 13y ago
I've built HTML/CSS/JS mobile apps with phonegap and while it's fun as a developer, the user experience is just not as good as building a proper native app. If you care about user experience, build using what is native to the platform. This is why most web devs don't build web apps using Flash or Java applets anymore. Those aren't native to the platform and don't provide the best possible user experience. HTML/JS as "native" apps to a platform can absolutely work and be awesome, but it really comes down to what "native" on a given platform means. On Android it's Java, on iOS it's Obj-C, on Windows it's C#, on a web browser or Firefox OS it's HTML/JS.
- rhelmer 13y ago
  Thanks, I appreciate the details. There definitely is a "happy path" for each platform, where tools/docs/developer support and getting into the marketplaces and so forth is much simpler and well-understood - things can get dicey when you stray from that.
zanny 13y ago
Using a document markup as your application structural layout, in an environment built around either static links or argument supplemented static links, with the concepts of forward and backward through a chain of pieces of content, I think is a really poor way to design applications. For a better UX and developer experience, that still uses JS, just look at QML. Declarative, application focused, and scriptable in JS. Easy to create one UI that transitions to other layouts, but the elements are first, not the text within them.