Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Now that Android 4.4 is almost released, I have a question. Does it make sense to build my app against the new version of API and release the updated version to the market? Or does it make sense only if I want to use any of the new features? What is the best practice or the recommended approach?
You should not worry about it. But if your app is a SMS app, then you might have to. Check out this article: http://android-developers.blogspot.nl/2013/10/getting-your-sms-apps-ready-for-kitkat.html
Like for any new Android version, you need to stay tuned to Google announcements, like the one that Alécio mentioned, as certain APIs could be deprecated/changed (in the case of KitKat, if your application depends on intercepting/reading/storing SMS messages, then you should read this). You also need to figure out whether you want to take advantage of any new API to make your application better in one way or another. It's also possible that a whole new feature could be introduced, one that could be interesting to your application. Just use your common sense.
Finally, to be able to use the latest version, you just need to download the latest SDK and ADT, and increment the targetSDKVersion number against the latest API level (this is a general good practice). The list of API levels, for each Android version, are available here.
Yeah..Earlier,you released your application with maximum sdk level is 17 above means, you don't have any problem with latest version..else,You released by 2.3 to 4.1 version means..You,should update your application also.Because APIs are different for above 4.1 and below 4.1. If required you need to update the latest APIs for Latest android version
No you do not need to make any change to your app in order to make it work on the newest version of android unless you use in your code deprecated classes or methods.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
This question is already asked by someone but that not feasible for now. My app is using minSdkVersion 26
targetSdkVersion 30 and crashing on Oppo and Nokia 6
You don't. First off look at your minSdkVersion- any device below that version won't work. So to make it work on everything you'd need to have minSdkVersion 1 (you might get away with 3 as that's the lowest commercially available device I know of). Then you'd need to only use functionality available on all those versions, so you would basically have to program to the 2010 version of Android. And even then there will be incompatibilities.
Instead, you decide on a version of Android that will support a large enough percent of the market in your target geographical area. You program to that. And then if you find specific incompatibilities you fix those.
As for the 2 versions you specified- Nokia6 can be as low as SDK version 25. So that may be why it isn't working. Oppo is a brand so you have to be much more specific there.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am willing to use retrofit 2.0.0-beta3
http://square.github.io/retrofit/
with the basic functionalities of the library , how ever i'm not sure whether for retrofit or generally it is same safe to use a library in beta stage with it's basic functionalities , as long as i tested it and it's working (but with out bench marking).
A pre-release of software that is given out to a large group of users
to try under real conditions. Beta versions have gone through alpha
testing inhouse and are generally fairly close in look, feel and
function to the final product; however, design changes often occur as
a result.
An early version of a program or application that contains most of the major features, but is not yet complete. Sometimes these versions are released only to a select group of people
So , In my opinion, Its not good to call Beta version .
Use stable version instead beta .
compile ('com.squareup.retrofit:retrofit:2.0.0-beta2')
is secure .
I think in general case, #Amiya is right, but I think in this special case, I would recommend Retrofit 2 beta.
http://inthecheesefactory.com/blog/retrofit-2.0/en
You may be curious that is it time to move to Retrofit 2.0 yet? Since it is still in the beta stage so you may want to stay with 1.9 first except you are an early adopter like me, Retrofit 2.0 works pretty great and there is no any bug found yet based on my own experiment.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I have a question concerning Android APIs.
1) Does the latest API (in Android) include ALL features (classes) from the earlier ones?
2) Is there any features, that got removed by a newer API? If yes, is there any website showing me the added/edited/removed features?
thank you :)))))
Does the latest API (in Android) include ALL features (classes) from the earlier ones?
Generally, yes.
Is there any features, that got removed by a newer API?
Sometimes, yes. Usually, what happens is that the resulting methods get marked as deprecated and do not do anything. Occasionally, stuff gets deleted from the class library outright.
If yes, is there any website showing me the added/edited/removed features?
There is an API differences report for each API release. For example, here is the report of the changes between API Level 20 and 21.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is there a drawback creating android applications using old sdk version? Other than the obvious one; you can't use the newer functions. Will this application slower if I set build target an old sdk compared to the latest api version when executed on a device?
Yes, not being able to use the new features is obvious. But it depends on what you are targeting and your user base is. In general, it depends on what you are trying to do. A game will usually want to use OPEN GL ES 2.0 so you need the android version that supports that. If you don't care about a specific feature it is best to follow this:
http://developer.android.com/about/dashboards/index.html
for an idea on a potential market share of an application. Older phones will increase the potential market. Besides versions you also need to know if you want to target an tablet or phone. That includes different UI changes/looks.
You won't be able to use new features, of course, if you don't need any new features there is no problem. You will also be able to deploy an application that users with older phones will be able to usecas well.
Cheers
There is no drawback other than not being able to use new features.
No, your application will not be slower.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
New devices support at least Android 4.0 and many people started to change their phones. Do you still think that we should target Android version 2.x?
I ask this because it won't be that easy for me to support 2.x because of my native libraries. I also have to buy Android 2.2 froyo device for my tests. So, I am trying to find out if all of the effort is feasible or not.
Gingerbread 2.3.3 is on 1/3 of active android devices so I think it is something to care about.
I've has same issue too. Resolved restricting some functionality like above:
int sdkversion = 6; //or whatever
if (Build.VERSION.SDK_INT<sdkversion){
...DO NOTHING ABOUT THAT FUNCTIONALITY...
} else {
...DO IT...
}
This should help you out :) I always check it out before embarking on a new idea.
http://www.appbrain.com/stats/top-android-sdk-versions
As for your native libraries, there are plenty of apps out there that only support 4.x versions and still do very well. There are some really decent devices that run gingerbread (2.3 I believe) and are perfectly suitable to all recent apps, but due to manufacturers wont be receiving an update.
Of course, various folk root their phones and use custom roms, so maybe it's not that bad afterall. These stats, can't take that into account, obviously.
HTH.