Going Native: Deciding between HTML5 and Native Apps. Almost every publisher I speak with these days is in the midst of developing, implementing or revising their mobile and tablet strategy. With technology changes coming faster than most can keep up, the mobile strategy you developed six months ago (post iPad 2 but pre-Kindle Fire) is most likely out of date. And with the news that there were more iPads than desktop computers sold in the fourth quarter of 2011, it’s no surprise that mobile strategy is on the top of everyone’s mind. Yet when speaking to publishers, I find lots of confusion. And the one topic that seems to cause the most confusion is the decision on whether to build native apps. Despite the near-religious debates that often arise on the topic, the decision on whether to go native app or not is based on a handful of straightforward questions you can ask yourself.
So, here’s a starting point for your decision tree on whether to go native. How many platforms do you plan to support? Will your app generate revenue? Is Apple planning a business app store? Why that would be a really good thing. 5 ways to wring more revenue out of your mobile apps — Mobile Technology News. What are some good examples of HTML5 mobile websites. HTML5 vs Native: The Mobile App Debate. Introduction Mobile apps and HTML5 are two of the hottest technologies right now, and there's plenty of overlap. Web apps run in mobile browsers and can also be re-packaged as native apps on the various mobile platforms. With the wide range of platforms to support, combined with the sheer power of mobile browsers, developers are turning to HTML5 as a "write one, run many" solution.
But is it really viable? Feature Richness Point: Native can do more We can divide mobile functionality into two dimensions: the experience of the app itself, and the way it hooks into the device's ecosystem, e.g. for Android, this would be features like widgets and notifications. In terms of app experience, native apps can do more. It's more than the in-app experience though. Counterpoint: Native features can be augmented, and the web is catching up anyway It's true that many in-app features are simply beyond reach for an HTML5 app. Making a hybrid - native plus web - app is hardly an ideal solution. Performance. What is the difference in user engagement between a browser-based mobile web experience (e.g. HTML5) and a native app built for Android or the iPhone. App Development Basics - How-To Help and Videos. Mobile Blog – Articles about iPhone, BlackBerry, Android and Windows Mobile Development.
Mobile Sites vs. Mobile Apps: Which is More Effective?: C&M* Browsing habits are changing. With the advent of faster data connections and smoother browsing experiences thanks to smartphones, a lot more of us are accessing sites through mobile devices. For the very same reason, we’re also using more mobile apps to do the things we want – and this is a relatively new phenomenon. This leaves content providers in something of a quandary, since not all brands have the luxury of being able to (or necessarily wanting to) offer both.
So they are faced with a choice: a) they optimise their site or launch a microsite for mobile browsing or b) or they develop an app to serve mobile content/services. Case in point: last month Boots announced its intention to develop and launch a new mobile platform in preference to an app, or series of apps, to serve its health and beauty offerings online. What are the advantages and disadvantages of such a strategy? We shall see. Breaking Down Mobile Browsing Click for a bigger image. Breaking Down Mobile Apps Last Word Resources. How to Make an HTML5 iPhone App. By Alex Kessinger You’ve been depressed for like a year now, I know. All the hardcore Objective-C developers have been having a hay-day writing apps for the iPhone.
You might have even tried reading a tutorial or two about developing for the iPhone, but its C—or a form of it—and it’s really hard to learn. I don’t want to say that you should give up on the objective: you can get it eventually. But in the meantime, there is something else that you can do. You can create a native app that lives with all the other apps, and for the most part, it’s going to be a pitch-perfect imitation.
You can do this with the skill set you probably already have: HTML(5), CSS, and JavaScript. I’ll show you how to create an offline HTML5 iPhone application. Offline? What am I talking about when I say "offline"? The app should be as functional as it can when it is offline, just like normal native mobile apps. Yeah, I mean it, check out the following image. Prework About the App Icon and Startup Screen Screen Size <! Why should I build a mobile app targeting a specific platform vs develop a mobile HTML5 website. Mobile App Marketing Platform for Acquiring App Users | Fiksu.
Leading mobile developer: “No more free apps” – a sign of things to come? I’ve written and tweeted about the phenomenal work that Simon Maddox has done over the years. His name will be familiar to many mobile developers given that Simon was amongst the first in the United Kingdom to get stuck into the mobile development scene. His CV, therefore, reads like a Who’s Who in mobile. He’s very much like a one-man A-Team, though. (If you can find him, and no one else can help, maybe you can hire The Maddox). Today’s post is a Q&A with Simon around the rather challenging discussion of paid-vs-free.
Here’s what happened. Let’s get started. Simon, could you introduce yourself and give us a flavour of the kind of things you’ve been working on over the past few years? I’ve been a freelance mobile developer, focusing primarily on iOS, for the past year and a half. Now, talk to us about 0870 — it was a runaway success in the context of mega-downloads and lots of money saved — tell us about the app. The premise behind 0870 is fairly straightforward. Not much at all. Do it. Mobile app development for Nokia, iPhone, Android, Windows and Blackberry. bolser, Leeds. "multi-platform app specialists" While most agencies were only just finding their way around a website, we were already going mobile.
From our early days specialising in Symbian for Nokia we now produce a wide range of mobile apps covering the world’s largest platforms. From iOS and Android through to Windows and Blackberry, our in-house team are responsible for some of the best known consumer branded apps. We can also cater for the increasing demand for HTML5 across all mobile projects and have a dedicated, specialist team responsible for this workstream. We have created more than 75 apps to date and have had over 6 million downloads Worldwide. Covering innovative, highly interactive and beautifully designed apps through to complex ‘back end’ architecture and development solutions, we pride ourselves in leading our clients through what can be a complex and at times costly process. We always demonstrate the value of our experience through high numbers of downloads, interactions and ROI.
Best practice for mobile apps. August 23, 2011 Jeannette Kocsis is senior vice president of digital marketing for The Agency Inside Harte-Hanks By Jeannette Kocsis It was recently announced by Nielsen that 37 percent of U.S. mobile consumers own smartphones. Of those consumers, 36 percent own Android devices, followed by 26 percent on iPhone and 23 percent on BlackBerry. Due to the iPhone’s maturity in the applications market, iPhone users have many more apps to choose from than the other devices. Rap on appMobile apps are becoming so commonplace that brands are being evaluated by consumers based on whether they have an app and how good or bad it is. EffectiveUI and Harris Interactive performed a study last fall and found that 69 percent of people surveyed indicated that a bad experience with a brand’s mobile application results in negative perception about the brand.
Also, 73 percent of mobile users surveyed said that they expected a brand’s mobile app to be easier to use than their Web site. Mobile apps are different.