{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 劫难 的问题《Are android apps backwards compatible?》','https://www.manongdao.com/q-285400.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm doing a bit of iPhone / Android development at the moment and I was curious, if I were to build an application that targets Android 2.2 and release it on the Android Marketplace, would it be playable by users who are using older versions of the OS, such as 1.6? What would happen if such a user were to attempt to run the app? Would they be prompted to update their OS or just receive an error message?
Thanks guys.
The android SDK is completely backward compatible using the mechanism that @Graham mentions. The other question will be "how far should you go". Use this graph to see the population of users on each platform level.
http://developer.android.com/resources/dashboard/platform-versions.html
This is pure opinion, but I would advise starting your app at API levels 7 or 8. The benefits of the APIs in EClair+ are worth losing this 0.4% still on 1.x devices.
If you are targeting 2.2, users with earlier SDK will not be able to download it.
They will see:
This app is Incompatible with your device XXXXXXXIt depends what you have in the
minSdkVersionfield in yourAndroidManifest.xml. If it is set to 4 or lower, then it will be visible to people using 1.6.There's a good explanation here.