Why doesn't HTML5 include support for camera input, accelerometer, compass & voice commands? How long before these are integrated?
What’s the Future? Native Apps or Mobile Web Apps?
21–30 of 38 posts
Re: What’s the Future? Native Apps or Mobile Web Apps?
#22> Can you name one great application the last 10 years that wasn’t a web app or a game? Yes. Scrivener.
TextMate
Re: What’s the Future? Native Apps or Mobile Web Apps?
#23Earlier quoted context omitted.
Chrome, Firefox, OneNote, Sharepoint, iTunes, Windows Media Center, Camtasia, VMWare, Git, Garage Band, Final Cut Pro, CS5+, True Crypt, Visual Studio 2010, ... The list can go on and on (although some might be slightly older than 10 years old).
Actually, most of these applications are more than 10 years old. And back-end systems, develompent tools and heavy duty media creation apps can hardly be compared to something that's a candidate for a web app.
So as long as you exclude apps that are lousy as web applications then all new good apps are web applications? How pragmatic.
Re: What’s the Future? Native Apps or Mobile Web Apps?
#24As a developer, I hope html5 apps end up being the norm, but one key difference between desktop apps and mobile apps is that you pretty much always have your phone with you. As a consumer, I love web apps because I can access them from anywhere and dont' need to have my computer with me. But if I always have my smart phone with me, what's my incentive to prefer a web app to a native one, especially one that syncs to the cloud?
Re: What’s the Future? Native Apps or Mobile Web Apps?
#25[deleted]
Re: What’s the Future? Native Apps or Mobile Web Apps?
#26At the moment, it looks like the trend is towards fragmentation in mobile platforms. A lot of companies are jumping on the mobile bandwagon, and they're not all adopting Android. I don't know if this trend will continue, but even with the current level of fragmentation, developing web apps seems very attractive.
Already, developing the same app for the iPhone, iPad, Android phones, and Android tablets is an expensive prospect. Appcelerator helps, but it's not a perfect solution, in part because it doesn't and probably never will support every platform.
With HTML/CSS/JS, on the other hand, you get cross-platform compatibility for free. "But," you say, "not all mobile devices have good support for web technologies!" This is true, but I think we can expect that to change. Support for the web should constantly improve across all platforms over time.
Since I prefer to invest in the technological long-run, I'll put my money on web apps except when native-only features are required. That way, instead of trying to port my app to an ever-increasing number of platforms, an ever-increasing number of platforms will--of their own accord--come to support my app.
Re: What’s the Future? Native Apps or Mobile Web Apps?
#27Why do people need there to be only one winner? It's going to be both web and native. Performance matters and web simply aren't up to it for a long time to come. Even with WebGL etc.
The article isn't about picking a winner, it's about what the current pros and cons are of choosing each as your platform for development.
Understanding the tradeoffs is important because we don't have unlimited development resources.
Re: What’s the Future? Native Apps or Mobile Web Apps?
#28Why doesn't HTML5 include support for camera input, accelerometer, compass & voice commands? How long before these are integrated?
Because it will never end. Today it's camera, accelerometer, compass, and voice commands... tomorrow it'll be something else.
Right now, since apps are predominantly native, a vendor can add new hardware and capabilities to their devices without the prior blessing of a standards body. Standards bodies will always be several years behind the state of the art in features, which means anything really compelling and new will always be in native form.
Re: What’s the Future? Native Apps or Mobile Web Apps?
#29What's the future?
i) Trains
ii) Cars
iii) Buses
iv) Airplanes
v) Subway
vi) Trolleybus
vii) Segway
viii) Helicopters
ix) Others
I don't have an answer yet.
Re: What’s the Future? Native Apps or Mobile Web Apps?
#30Earlier quoted context omitted.
Chrome, Firefox, OneNote, Sharepoint, iTunes, Windows Media Center, Camtasia, VMWare, Git, Garage Band, Final Cut Pro, CS5+, True Crypt, Visual Studio 2010, ... The list can go on and on (although some might be slightly older than 10 years old).
Actually, most of these applications are more than 10 years old. And back-end systems, develompent tools and heavy duty media creation apps can hardly be compared to something that's a candidate for a web app.
Had to look it up, and only three were older than 10 years old. VS (going back to the first version), VMWare, and Final Cut Pro).
Chrome (2008)
Firefox (2004)
OneNote (2003)
Sharepoint (2001)
iTunes (2001)
Windows Media Center (2002)
Camtasia (2002)
VMWare (1999)
Git (2005)
Garage Band (2004)
Final Cut Pro (1998)
Creative Suite (2003)
True Crypt (2004)
Visual Studio (1995)