3 ms·
Use the right tool for the right task. Using the wrong tool for the task does not mean that there is something wrong with the tool. You want to develop graphic
by placebo 10y ago
Use the right tool for the right task. Using the wrong tool for the task does not mean that there is something wrong with the tool.
You want to develop graphic intensive games using a single code base without learning native iOS or Android app development? You could probably do that with open source platforms like Gideros (there are good commercial alternatives too). Since iOS can't run LuaJIT, in particularly resource hungry games you might have no option but to code in native.
A few years ago I developed a game for both Android and iOS using Cordova and was very happy with the results. It was a Scrabble clone against the CPU with nice animations and no one could tell it was not native. I knew it was way below what the web view could handle so I wasn't surprised it succeeded. I'd have never tried it in the first place with a 3D game or a game with many entities and hope to get 50fps.
I also use Cordova to get native looking apps (not games) by using Framework7 (http://framework7.io http://framework7.io) - I'd like to see how many users would really notice the difference (I'd guess about the same amount of people who would complain about mp3's not giving a good enough quality for the music they listen to)
I do agree that Cordova apps will probably continue be treated like second class citizens (and perhaps worse) mainly because I assume it runs mostly against the interests of Apple and also Google who would prefer you invested your time getting locked in to their specific platform...
- WA 10y agoWhy Framework7 and not Ionic 2?
- placebo 10y agoFrankly, because I didn't want to learn Angular when I first encountered Ionic. Ionic might be great though, it's just that I have no experience with it yet to say one way the other.
- ivan_gammel 10y agoI had similar concern, but after trying F7 switched to Ionic 2 and learned Angular 2: F7 architecture isn't flexible enough and it's not production ready overall.
- LeoNatan25 10y agoIt only takes one look at the transparent navigation bar or popup or non-spring transition animation to notice something is "off". Further looking, things like inconsistent margins across devices, non-standard controls, etc. give it away on a fundamental level. This kind of disrespect for your users' ability to notice crap is what I dislike most about lazy cross-platfom developers. At least have the decency to admit your are churning a technologically and experience-wise sub-par product for this and that reason, but that almost never happens. It's always the "no one notices this" nonsense.
- WA 10y agoI've seen too many native apps with strange user interfaces, colors, margins, wrong transitions to still believe that people really care. Most non-dev users want to get some stuff done via apps and don't care about design details.
- placebo 10y agoDisrespecting your users has very little to do with the tool you use and everything to do with how you use it. One can also be pedantic/fanatic about going by the book to the letter in order to conform with every one of the platform UI's "laws" and still generate a crappy application due to lack of insight on what will be intuitive or useful to the end user. No - a sub-par product will mostly have a sub-par developer responsible. Quality and craftsmanship will come across no matter what technology you decide to use. That's not to say that a good developer couldn't produce an even more polished experience with native programming, but as mentioned before, I doubt the difference is noticeable enough for many applications to justify the dramatic increase in learning curve and maintenance.
- Turing_Machine 10y ago"This kind of disrespect for your users' ability to notice crap is what I dislike most about lazy cross-platfom developers." A lot fewer people actually care about UI minutia than you imagine.