satisfactory, so you've waded through the native app versus responsive
website argument and based on the needs for your needs and your
enterprise, you decide you need a native app. The next thing to number
out is the age-old question: "iOS or Android?"
Part of the adversity surrounding native app development is that it's a allotment of work to develop for one stage — let alone two or three. whereas iOS and Android aren't the only two players in the mobile space, for better or worse, they are the two most dominant. It's significant to recall that other mobile stages do exist, but to hold this item from going too long, for now, we'll just aim on iOS and Android.
Even as lately as a year before, inquiring the inquiry, "iOS or Android" would lead me to state, almost without hesitation, "iOS first, then Android."
Today, the answer is a bit more perplexing. Android is the superior wireless functioning system on a global perspective (though the two are much closer in marketshare in the U.S.) and it beat apple fruit to the 1 million apps mark. Moreover, with the achievement of phones such as the Samsung Galaxy S4, emblem persona around Android is growing by the day.
My advice tends to be to plan on both an iOS and Android app for most companies, if you believe you need a native mobile app. That doesn't signify you have to launch with both at the same time, but both should be on your supreme timeline.
• What are your current users utilising? gaze at your tourist stats and glimpse what portion of your mobile visitors are approaching from Android or iOS. If you see a higher mobile commitment rate from iOS users, it's a good concept to start with them first. On the flipside, if most of your users are on Android, starting there might make more sense.
• What are your tablet plans? whereas Android is the dominant wireless functioning scheme, it has not taken off on tablets in the identical way. Google might boast that Android tablets have almost half the international market, but when you gaze at how those tablets are utilised — or at the usage share amidst tablet apps, it's clear the iPad is the winner. The one exclusion is Amazon's Kindle blaze, which sprints a forked type of Android — and thus is sort of in its own category. If you plan on creating a tablet know-how, aim on iOS first.
• What are your developers familiar with? Even though most companies end up contracting out a good chunk of their mobile development work, it's worth talking to your team and seeing what they are most well known with evolving in. Developing for iOS requires a Mac (you can work round this but at some stage you'll need a Mac) and Android's developer devices — while advancing — are not at Xcode levels just yet.
• Do you desire to ascribe for your app? The adage that Android users never pay for apps isn't quite as factual as it utilised to be, but it's absolutely true that iOS users are more eager — and more expected to pay — for an app than Android users. That shouldn't put you off of using Android — there are still plenty of ways to monetize that scheme — but for an initial launch, it desires to be considered. furthermore consider where you can accept payments from both platforms. Google is continuing to boost the number of countries that support paid Google Play apps but this is an area where apple fruit still has a considerable lead.
Why beginning With iOS Can Make Sense
Most foremost apps still launch on iOS first. This usually has little to do with iOS being superior to Android, rather than, it's just a component that aiming at an iOS app is normally less awkward than an Android app.
One of Android's benefits is that it is available to anyone and on a gigantic swath of apparatus. Unfortunately, that can furthermore be a difficulty, particularly for a developer with limited assets.
At the time of this writing, the most of Android apparatus finally support Android 4.0 Ice elite Sandwich or subsequent, with a full third running Android 4.1.x Jelly Bean. That's gigantic report and is a large-scale improvement over even just the last six months.
The difficulty is, there are still 33% of users utilising some type of Android 2.3.x Gingerbread, an OS released in 2010. Some of the best and most intriguing Android characteristics are not available on that older type, which means that if you desire to evolve for Android, you need to conclude: Should I goal only newer users or should I furthermore target older apparatus as well?
The response to this inquiry will likely largely depend on your market and your position. If you're in the joined States, I suggest to target Android 4.0 or larger. If you have items of users in Europe or Asia, the situation might be distinct.
Meanwhile, whereas there is certainly some fragmentation on the iOS edge, the most of iOS users improvement to the newest OS type nearly instantly.
If you construct an app for iOS 6, you can know that it will work on the iPhone 3GS all the way to the newest iPhone 5 and the iPad 2, iPad 3, iPad 4 and iPad mini. furthermore, because apple fruit controls the hardware and software, you don't have to concern about matters such as dissimilarities in computer display tenacity or graphics processor or support for X, Y, or Z. You still need to test on every apparatus, but the number of devices to test is much, much smaller.
A large-scale inquiry mark is the upcoming release of iOS 7. iOS 7 has some important UI changes whereas it will run on every iPhone and iPad currently being traded, it won't work on some older devices. Still, for businesses looking at evolving a new app today, I would still powerfully suggest conceiving an iOS 7-only app. It's a bold move but from the developers I talk to on a daily cornerstone, it's going to rapidly become the norm for more and more high profile apps. Moreover, the design for iOS 7 is so distinct, any app that isn't conceived using that new language will gaze out of date.
Depending on what type of app you're conceiving, this is where a cross-platform framework such as Appcelerator or Sencha feel or Phonegap can become helpful.
It's important to remember, although, that is your app really needs to do a alallotmentment of native functionality — or if it handles a lot of facts and figures — there is no substitute for going native.
not anything is poorer than having an Android app with iOS-style buttons or an iPhone app that is slow as molasses because it's just a web sheet in a wrapper that examines like an app.
Native apps take a alallotmentment of work. Full halt. Make sure you can make the buying into before getting begun.
On the flipside, there is furthermore some unbelievable Android-first development happening too. Moreover, the fact that the Google-branded apps are so good on Android is often a cause that purchasers proceed Android first.
The reality with wireless apps is that you won't understand everything you need to understand until you get your app in a marketplace — any marketplace. Try your hand at iOS or Android and then take what you discover to put in the issue for the next platform. If you glimpse little commitment or use on one platform — you can always cease the app and opt for a more wireless first world wide world wide web experience.
 |
| ios vs android |
Part of the adversity surrounding native app development is that it's a allotment of work to develop for one stage — let alone two or three. whereas iOS and Android aren't the only two players in the mobile space, for better or worse, they are the two most dominant. It's significant to recall that other mobile stages do exist, but to hold this item from going too long, for now, we'll just aim on iOS and Android.
iOS, Android or Both?
Even as lately as a year before, inquiring the inquiry, "iOS or Android" would lead me to state, almost without hesitation, "iOS first, then Android."
Today, the answer is a bit more perplexing. Android is the superior wireless functioning system on a global perspective (though the two are much closer in marketshare in the U.S.) and it beat apple fruit to the 1 million apps mark. Moreover, with the achievement of phones such as the Samsung Galaxy S4, emblem persona around Android is growing by the day.
My advice tends to be to plan on both an iOS and Android app for most companies, if you believe you need a native mobile app. That doesn't signify you have to launch with both at the same time, but both should be on your supreme timeline.
Deciding Which to Launch First
If you can't afford to simultaneously develop for iOS and Android, you have to make the conclusion of what scheme to goal first.
Here are some components to consider when concluding which stage to goal for an primary issue:
Here are some components to consider when concluding which stage to goal for an primary issue:
• What are your current users utilising? gaze at your tourist stats and glimpse what portion of your mobile visitors are approaching from Android or iOS. If you see a higher mobile commitment rate from iOS users, it's a good concept to start with them first. On the flipside, if most of your users are on Android, starting there might make more sense.
• What are your tablet plans? whereas Android is the dominant wireless functioning scheme, it has not taken off on tablets in the identical way. Google might boast that Android tablets have almost half the international market, but when you gaze at how those tablets are utilised — or at the usage share amidst tablet apps, it's clear the iPad is the winner. The one exclusion is Amazon's Kindle blaze, which sprints a forked type of Android — and thus is sort of in its own category. If you plan on creating a tablet know-how, aim on iOS first.
• What are your developers familiar with? Even though most companies end up contracting out a good chunk of their mobile development work, it's worth talking to your team and seeing what they are most well known with evolving in. Developing for iOS requires a Mac (you can work round this but at some stage you'll need a Mac) and Android's developer devices — while advancing — are not at Xcode levels just yet.
• Do you desire to ascribe for your app? The adage that Android users never pay for apps isn't quite as factual as it utilised to be, but it's absolutely true that iOS users are more eager — and more expected to pay — for an app than Android users. That shouldn't put you off of using Android — there are still plenty of ways to monetize that scheme — but for an initial launch, it desires to be considered. furthermore consider where you can accept payments from both platforms. Google is continuing to boost the number of countries that support paid Google Play apps but this is an area where apple fruit still has a considerable lead.
Why beginning With iOS Can Make Sense
Most foremost apps still launch on iOS first. This usually has little to do with iOS being superior to Android, rather than, it's just a component that aiming at an iOS app is normally less awkward than an Android app.
One of Android's benefits is that it is available to anyone and on a gigantic swath of apparatus. Unfortunately, that can furthermore be a difficulty, particularly for a developer with limited assets.
At the time of this writing, the most of Android apparatus finally support Android 4.0 Ice elite Sandwich or subsequent, with a full third running Android 4.1.x Jelly Bean. That's gigantic report and is a large-scale improvement over even just the last six months.
The difficulty is, there are still 33% of users utilising some type of Android 2.3.x Gingerbread, an OS released in 2010. Some of the best and most intriguing Android characteristics are not available on that older type, which means that if you desire to evolve for Android, you need to conclude: Should I goal only newer users or should I furthermore target older apparatus as well?
The response to this inquiry will likely largely depend on your market and your position. If you're in the joined States, I suggest to target Android 4.0 or larger. If you have items of users in Europe or Asia, the situation might be distinct.
Meanwhile, whereas there is certainly some fragmentation on the iOS edge, the most of iOS users improvement to the newest OS type nearly instantly.
If you construct an app for iOS 6, you can know that it will work on the iPhone 3GS all the way to the newest iPhone 5 and the iPad 2, iPad 3, iPad 4 and iPad mini. furthermore, because apple fruit controls the hardware and software, you don't have to concern about matters such as dissimilarities in computer display tenacity or graphics processor or support for X, Y, or Z. You still need to test on every apparatus, but the number of devices to test is much, much smaller.
A large-scale inquiry mark is the upcoming release of iOS 7. iOS 7 has some important UI changes whereas it will run on every iPhone and iPad currently being traded, it won't work on some older devices. Still, for businesses looking at evolving a new app today, I would still powerfully suggest conceiving an iOS 7-only app. It's a bold move but from the developers I talk to on a daily cornerstone, it's going to rapidly become the norm for more and more high profile apps. Moreover, the design for iOS 7 is so distinct, any app that isn't conceived using that new language will gaze out of date.
Cross-Platform Toolkits
despite of what system you start with, it's not uncommon for enterprises — particularly small enterprises — to desire to limit the allowance of code they have to compose for both versions of an app.Depending on what type of app you're conceiving, this is where a cross-platform framework such as Appcelerator or Sencha feel or Phonegap can become helpful.
It's important to remember, although, that is your app really needs to do a alallotmentment of native functionality — or if it handles a lot of facts and figures — there is no substitute for going native.
not anything is poorer than having an Android app with iOS-style buttons or an iPhone app that is slow as molasses because it's just a web sheet in a wrapper that examines like an app.
Native apps take a alallotmentment of work. Full halt. Make sure you can make the buying into before getting begun.
Will Apple (or Google) go wrong?
The
second part of Theo's inquiry was really about the long-term viability
of app stages. I'm not the astonishing Kreskin and I can't forecast the
future, but from how the world examines now, betting on either Android
or iOS is not going to be a problem. apple fruit has an entrenched
ecosystem and hundreds of millions of trusted customers.
Could that dry up and go away tomorrow? Absolutely. gaze at Nokia. gaze at BlackBerry. Still, I wouldn't wager on that happening any time in the near future.
With Google, it's the identical thing. Yes, most people believe of Samsung when they discover "Android" rather than Google — and yes, that is a difficulty — but Android is growing and is on fire.
Could that dry up and go away tomorrow? Absolutely. gaze at Nokia. gaze at BlackBerry. Still, I wouldn't wager on that happening any time in the near future.
With Google, it's the identical thing. Yes, most people believe of Samsung when they discover "Android" rather than Google — and yes, that is a difficulty — but Android is growing and is on fire.
It's OK to Just Pick One
While
I sustain that for most little businesses and emblems, a dual-OS
approach is best, it's alright to just pick one platform if you don't
have the money to make it work.
Plenty of developers do very, very well just focusing on iOS. In detail, part of what keeps me trusted to iOS as a stage is the fact that those apps are iOS only.
Plenty of developers do very, very well just focusing on iOS. In detail, part of what keeps me trusted to iOS as a stage is the fact that those apps are iOS only.
On the flipside, there is furthermore some unbelievable Android-first development happening too. Moreover, the fact that the Google-branded apps are so good on Android is often a cause that purchasers proceed Android first.
The reality with wireless apps is that you won't understand everything you need to understand until you get your app in a marketplace — any marketplace. Try your hand at iOS or Android and then take what you discover to put in the issue for the next platform. If you glimpse little commitment or use on one platform — you can always cease the app and opt for a more wireless first world wide world wide web experience.
No comments:
Post a Comment