4 ms·
I feel we’ve gone too far in emulating native apps. Conceding defeat will force us to rethink the web’s purpose and unique strengths — and that’s long overdue.
by pavlov 11y ago
I feel we’ve gone too far in emulating native apps. Conceding defeat will force us to rethink the web’s purpose and unique strengths — and that’s long overdue.
This, a million times. Mobile websites and mobile apps have completely different strengths. The current trend is to develop them both with the same HTML-based toolchains and make them as similar as possible, which ends up being to the detriment of both.
Users don't want mobile apps that are simply a website packaged up behind the "icon on the homescreen". Those apps lack the essential benefits of native: fast and seamless access, smart use of local data, integration with device services like notifications...
There's nothing more annoying to a mobile user than an "app" that takes 10 seconds to start up because it first loads a browser engine, then makes a hundred HTTP requests to fill up that embedded browser with content. (And if the 3G network happens to be clogged, the app may end up showing nothing after 20 seconds.)
For developers, Cordova/PhoneGap-style tools are not a panacea either. It's easy to get an 80% solution done, but then you run into problems with mobile browser performance, browser differences between devices (even Android devices with the same base OS can have very different web view browser engines), etc. With all that, the last 20% of a Cordova app may well take 80% of development time, and that's rarely been budgeted in.
Shameless plug: my startup Neonto makes a UI design tool that creates usable iOS and Android code from visual layouts. It's a great way to remove the friction in creating real native apps:
http://neonto.com http://neonto.com
- soft_dev_person 11y ago"With all that, the last 20% of a Cordova app may well take 80% of development time, and that's rarely been budgeted in." To be fair, that could be said about most software projects. "80% done, now the last 80% remains." Not that I disagree with you, I had the same experience trying to make an Android app in Phonegap. It's lacking, like most cross-platform frameworks (for most types of apps, but typically not games) I have tried. They are only suitable for basic stuff where the native feel isn't critical.
- pavlov 11y agoTo be fair, that could be said about most software projects. Yes, absolutely true. The difference here is between "known unknowns" and "unknown unknowns", to paraphrase a certain renowned military strategist... With Cordova/PhoneGap, it's easy to get the initial impression that you're dealing with "known unknowns", just the typical web development project pitfalls -- "This is HTML, I know this stuff". When the "unknown unknowns" hit the fan, it's often pretty late in the development cycle, and so things blow past original estimates even though they were competently planned. It's just that the plan was for web development, not the shifting art of websites-in-drag-pretending-to-be-apps-development.
- jkestner 11y agoI agree with that. With an abstraction layer on top of a native layer, inevitably you have to go below the surface unless you fit the intended use case perfectly. I learned this lesson with the Objective C-Python bridge. Spent needless time mapping differences between the two to the point where I had to learn Objective C anyway.
- wpietri 11y agoI agree, but one minor nit: when major problems crop up "pretty late in the development cycle", this typically means a waterfall development cycle. Waterfall approaches are really only appropriate when there's nothing particularly risky. I plead with the HN audience: never let a manager choose the waterfall model by default. They often happen because they make contract negotiation easy. But that's only because they save all the trouble for later.
- touristtam 11y agoside comment: the rule is called the 90-90 rule [https://en.wikipedia.org/wiki/Ninety-ninety_rule https://en.wikipedia.org/wiki/Ninety-ninety_rule]
- jsingleton 11y agoWhat do people think of frameworks like https://jquerymobile.com https://jquerymobile.com and similar? I tend to think it's good when running in a browser but not when it's made mobile web app capable and running full screen without native controls. Unless it's a super simple single page app. At the other end there are things like Instagram where you basically can't do anything on the website (can't sign-up, can't upload photos). Everything requires the app.
- fabean 11y agoI absolutely hate jquerymobile, you should just make your website responsive with CSS media queries then pepper in a little bit of javascript to handle things like slide out navigations.
- k__ 11y agoI read that Appcelerator Titanium and NativeScript are a much better way. You can use much of your JavaScript skills and still get to go native.
- joshstrange 11y agoUnless that platform has changed completely in the last year or so then they are wrong. Appcelerator (and things like it) generally make "Hello World" super easy and even the first week or two will be awesome. Then the cracks will start to show. You will add a listener on a button and the app starts crashing with a cryptic error, you start having to litter your code with `if(isAndroid)`/`if(isIOS)`, or for some reason a view will be really show to render to lag between clicking and doing something. When you get down to it you'd be better off learning native or just accepting a mobile website instead. Normally (IMHO) the only apps worth using appcelerator for are simple websites and at that point you'd be better off just doing a mobile website. I'm excited to play with React Native but I fear it will suffer from the same issues.
- untog 11y agoI agree with most of what you say, but: you start having to litter your code with `if(isAndroid)`/`if(isIOS)` That's an inevitable drawback of a cross-platform framework like this. XCode and Android Studio only work with one OS, so they sidestep it.
- k__ 11y agoSidestepping a problem in universal app development by don't doing it. You're joking right? ;)
- thekingshorses 11y agoI agree with PPK, but sorry to say this: you are just throwing garbage. > There's nothing more annoying to a mobile user than an "app" that takes 10 seconds to start up Try this on your mobile browser http://hn.premii.com/ http://hn.premii.com/ Now download this. Android : https://play.google.com/store/apps/details?id=com.premii.hn https://play.google.com/store/apps/details?id=com.premii.hn Or iOS: https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://itunes.apple.com/us/app/hacker-news-yc/id713733435 And play with it. Download top 5 native HN apps, and launch those, and tell me which one takes 10 seconds on which device. No doubt that you will have to deal with different version of webkit browsers (webview) on android. As long as you follow standards and not use latest CSS rules, you will be fine. And with Android 5.0+, its much much better. --- Now try this page on your mobile, and tell me how bad it is. This is few hours of work (Flipboard style animation), and works on iOS/Android Chrome/WP8: http://reddit.premii.com/#/r/news http://reddit.premii.com/#/r/news There are issues with browsers, but performance is not one of the issue. ---- It takes time on Cordova not because of HTML, but because how each platform works natively. I am not a native developer.
- pavlov 11y agoI don't see the point of comparing HN apps. HN is a website and doesn't do anything meaningful as an app. Android 5.x has less than 10% marketshare, and 4.x seems quite resilient in low-end devices. It's going to take a while until you can build hybrid apps exclusively for Lollipop. If you don't think mobile browsers have performance issues, you must use high-end devices exclusively.
- thekingshorses 11y agoWhat is meaningful app? Twitter is list of stories with notifications. For me its more like HN app. HN has list of stories, Twitter has 140 characters tweet. When you click on the HN story, you get list of comments or article. When you click on the tweet, you get replies and retweets and so on. Facebook is a same thing with pictures and videos. Try this http://reddit.premii.com/#/r/pics http://reddit.premii.com/#/r/pics - enable pictures view from top right dropdown and http://reddit.premii.com/#/r/gifs http://reddit.premii.com/#/r/gifs to try gify/video --- I didn't start with Android 5.x. I started my app with Android 4.x. I don't think you use low end Android device. Even native apps on Android has lot of issues related to performance. On my Nexus 5.0/Android 5.x, Facebook scroll is not smooth when there are pictures. I only get non-important notifications from my twitter app. I test my app in first generation of iPad 2 (My iphone 4s broke) and galaxy s3. --- Now show me 5 meaningful 100% native apps (Non-game) that are not developed my a startup with a huge capital or big company, available on iOS and Android, and has 4.x star ratings.
- nostrademons 11y agoBoth Android Studio and XCode will give you usable iOS and Android code from visual layouts. I've found that usually the easiest way to prototype an interface is just to build it for real - it's faster than Photoshop, even. The hard part about X-platform mobile development is that oftentimes you need different product concepts on Android & iOS, because the idioms, best practices, device capabilities, and user expectations are different on each platform. So your client generally has to be ground-up development by an experienced expert in the platform, you can't just take the same layout and make it run on both.
- pavlov 11y agoBoth Android Studio and XCode will give you usable iOS and Android code from visual layouts. Well, for some definitions of "usable" and "visual layouts"! Our goal is to make a designer's tool that can output complete, store-ready projects for simple apps and for both platforms. That includes three things that neither Xcode nor Android Studio does: 1) Interface Builder and Android Studio's layout editor are not meant for designers. (Seriously, try giving them to a Photoshop-educated designer.) 2) Xcode and Android Studio let you define views, but neither of them produces the controller-level code from visual designs. (We do that and also produce model-level code for simple apps; there's a plugin API for more complex situations, or you can of course do that in handwritten code.) 3) Cross-platform. Anything you do in Xcode or Android Studio needs to be rebuilt from scratch on the other platform. ...the idioms, best practices, device capabilities, and user expectations are different on each platform. I feel that this doesn't hold true anymore. iOS 7+ and Android 4+ have largely converged on a flat style where a 3rd party app can define its own style that is easily compatible with both. With Windows 10, even Microsoft is coming into this "common mobile" UI fold. They're giving up on the idiosyncratic (and interesting) Windows Phone concepts, and instead adopting a generic look that makes it easier to port Android/iOS apps directly. They're also offering new APIs and runtimes for that. (Edit: To clarify, you can customize layouts separately for iOS and Android in Neonto Studio.)
- leonatan 11y agoI'm sorry, after reading you say "they are now the same because they are flat", I sincerely hope you fail. You are clearly not a designer, yet attempt to market a development tool as such.
- joeyspn 11y ago> For developers, Cordova/PhoneGap-style tools are not a panacea either. It's easy to get an 80% solution done, but then you run into problems with mobile browser performance. That is a thing of the past. At the current rate of smartphone/phablet specs growth the differences with desktop are laughable (you can currently get 64bit octacore@1.7Ghz mobile devices with 3Gb of RAM for around $100) [0]. And this will only continue to grow. 16core and 32cores will be here in 2-3 years [1]. IMO, hybrid apps are already the present. The difficult times when we didn't have the required performance in our pockets are long gone... and frameworks like Ionic are really convenient for certain use cases. > browser differences between devices (even Android devices with the same base OS can have very different web view browser engines) That has been already solved with xwalk [2]... but again, this will be irrelevant in a couple of years. [0] http://www.gearbest.com/cell-phones/pp_152602.html http://www.gearbest.com/cell-phones/pp_152602.html [1] http://www.xbitlabs.com/news/cpu/display/20130304235830_President_of_ARM_Foresees_16_Core_32_Core_Chips_for_Smartphones.html http://www.xbitlabs.com/news/cpu/display/20130304235830_Pres... [2] https://crosswalk-project.org/ https://crosswalk-project.org/
- throwaway2048 11y agothe amount of cores makes no difference when javascript is single threaded. Infact its often detrimental especially on mobile because each individual core is significantly weaker. Plenty of websites doing advanced html5 gunk bring top of the line systems to their knees.
- joeyspn 11y agoOk, valid point... But still the Ghz's per core are also increasing, and with that the overall performance. If you've used webapps like Popcorn-time or Slack you'll understand what I'm trying to say. Are they native? No, they're JS apps Do the users care? No, cos they do the "job" pretty well We're reaching that computing power with mobile devices. In fact current mobiles are like desktops of 3/4 years ago. For certain kind of apps it won't matter if they're built with web technologies. (I'm not saying that you should bet on WebGL vs OpenGLES) It's all about the use case.