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've been looking at a few ActionBar scripts that support SDK 1.6 and above. Here's the three main ones I'm looking at:
https://github.com/johannilsson/android-actionbar
http://github.com/JakeWharton/ActionBarSherlock
http://android.cyrilmottier.com/?p=240
Which one do you recommend? or if you have another suggestion, let me know.
ActionBarSherlock is great library I've used it on several projects from Android 2.1 to 4.0 (it;s compatible to 1.6), the dev Jake Wharton is great at including the latest features from the Android compatibility library very quickly.
Here's a link to the demo app useful for seeing some of the things you can do with it.
I recommend google ioschedule app pattern. You could download it's source code.
Why not just use the actionbar that is provided in the backward compatibility api?
Related
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 2 years ago.
Improve this question
Some friends of mine and I are developing an App as a school project in Android Studio because the only language we currently speak is Java, and we don't know how to work as Team e.g. How do we share the code with all of us, or if we shall do it with GitHub how does that work too? We have little experience in these things and would appreciate it a lot if you could help me what we could do and what is the best way to proceed
You need a distributed version control system.
The most common version control system is git, but svn and mercurial also exist.
Then the version control system needs a centralized way to distribute the latest changes to everybody. The most common is Github; there is also Bitbucket and Gitlab.
Since you ask very general questions, I think the easier way would be using Github because it is the most common, and it integrates fairly easily with Android Studio. Even when solving differences between files (conflicts), Android Studio offers some handy dandy dialogs to ease the editions.
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 quite eager to know the advantages of Kotlin programming language over Java for Android application development as I would love to explore new things. If any one have any knowledge about it please do needful.
Thank you.
I assume you asked about Kotlin versus Java for Android development.
Basically there are reasons to switch from Java to Kotlin for Android development:
Readable and concise code
Small runtime
Performance
Kotlin libraries
All this points described here:
Develop Android apps with Kotlin
Using Project Kotlin for Android
Checkout Awesome Kotlin for Android
You might be able to see it here：http://blog.jetbrains.com/kotlin/2016/02/kotlin-1-0-released-pragmatic-language-for-jvm-and-android/
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 8 years ago.
Improve this question
I have developed a simple app, using a webview. It crashes on APIs older than 11. I guess that I used some futures that are not supported on old APIs and that is why it isn't working.
Sometimes when I am changing my code in Eclipse it gives me error about this, but most of the times there's no error or warning.
I think it's a bug in Eclipse, how should I find the parts that are causing the problem.
I won't send any code because it is a general question of mine.
Your app is crashing on devices older than API level 11 due to ActionBar compatibility issues.
You will need to use support library appcompat_v7 to make your app with ActionBar run on devices lower than API level 11.
Here's a complete tutorial of using appcompat_v7 library :
http://android-er.blogspot.in/2013/12/create-dummy-app-extend.html
Official link :
https://developer.android.com/tools/support-library/setup.html
Hope this helps!
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 8 years ago.
Improve this question
2 years ago i developed an app on android 4.2.2. I was wondering if the statistics are still the same?
If I developed it on android 4.2.2 now would it still be the best option? Will it be the optimum to reach the most devices?
Or is there a newer version that is mastering the market?
Thanks in advance.
It is recomended that you always look at the market share of the Android versions to choose your entry version.
In the link below you can see the stats
https://developer.android.com/about/dashboards/index.html
As for today, I would recommend you to support API 15 and above (up to 21). It represents almost 90% of all devices, and as it represents Android 4.0, you can alredy use some Material design elements and use Fragments as you wish.
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
I'm just getting into some Android development, and came across Android Studio. I know it's pretty early days, but it seems relatively stable and I'm very familiar with JetBrains other tools (which it is based on), so it seemed a good fit.
However I'm finding that every tutorial or article I can find on Android development explains things in terms of Eclipse.
To me it seems that Android Studio will be the way forward, and so I'm relunctant to learn Eclipse only to have to migrate everything later.
So what are the technical limitations of each choice...
If I stay with Android Studio, what major differences will I need to be aware of when trying to make sense of tutorials designed for Eclipse.
...OR...
If I switch to Eclipse, how difficult will it be to move across to Android Studio later?