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 9 years ago.
Improve this question
I come from iOS development, with some basic android apps done,
now im using a android sherlock actionbar,
I dont have clear if this is the same in iphone [iOS] as a UINavigationBar?
thanks!
The Actionbar is an incredibly useful UI widget for Android, having roughly the same appearance as the UINavigationBar on iOS, except with Android specific UI paradigms (context menu integration, tabs, progress loaders and more).
You'll quickly discover though, that the Actionbar only existed natively from Honeycomb (Android 3.x) onwards. So how do we get the Actionbar into projects that use earlier Android versions?
Android's achilles heel is the massive and somewhat fragmented ecosystem. For some reason to do with economics, market demographics or perhaps pure disdain for developers, some manufacturers insist on making devices for Android 2.x - rather than the newer 4.x version of Android. In this instance it's better to use a third party library called ActionbarSherlock by Jake Wharton. ActionbarSherlock (ABS) is basically a support library that will enable most Actionbar features on versions earlier than 2.x, with a few extra options to boot.
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 7 years ago.
Improve this question
It's a good idea to use Google Material Design on a iOS project?
I'm working on a project that works on iOS and Android, on Android we use Material Design, but when I try to make things at same way on iOS, the UX is not so good, it's just my perception or someone had the same experience before?
From my experience with some of Google Apps, it's perfectly possible to use material design on iOS. Actually, Material Design is not a platform specific design.
It'll "break" the Look and Feel with the rest of the system? Yes, kinda. But you definitely can do that and achieve good results and nice UX.
Some good examples are: Youtube, Hangouts, Google Maps.
And a non-Google example: Homeslice.
Thing is, you're probably going to have to develop some components/widgets to achieve that.
You can read more about Material Design here. And there's a loooong discussion on this matter here.
Material Design is not specifically targeted towards a platform. Its a design specification with a set of guidelines to build any system. The guidelines are specified to achieve better UX.
So you should be able to build a material design themed application for any target devise. If you are specific to ios, you could get some inspiration by looking at some of the sample apps built based on the theme. Google inbox app or the material design sample app
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 have to make my app fully in material design. It should support pre-lollipop devices as well. I tried with one support library found here.
It works fine, but seems to be slow in effects like ripple effects. In some articles, I found we can use
compile "com.android.support:appcompat-v7:21.0.+1"
This dependency like here.
What is the right way to implement material design on older devices?
I want to use material items, like Floating action button and all.
MaterialDesignLibrary by navasmdc seems to be forgoten with 150+ issues reported. It's also known for its conflicts with other libraries, lack of support and poor widget implementation.
Basically it depends on what would you like to achieve. Most of material features is too heavy to be used on older platforms. If you wish to have FloatingActionButton, Toolbar, RecyclerView and theming, you can use the Design Support Library and AppCompat from Google.
If you wish to have shadows, ripples and others, you should look for open-source libraries. Ray's lib is a very good example. Check out awesome-android and Android Arsenal. Both have a good list of material libraries.
I have my own library as well. It's called Carbon and it backports most of material features to Android 2.2+.
I have used the support design library, for ripple effects and other good features use rey material library, you can also see navasmdc
Easy way to implement material design is to use open source libraries that supports all pre-lollipop devices.
Have a look at this and this.
There are many other libraries as well. You can google it.
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 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
Is there a possible to use actionbar with tabs and the collapsed action menu in one row
like in the image:
I would like to use standard android actionbar ,not the 3rd party lib.
Yes, it is quite possible to do that without using a third party library. However, it will diminish your backward compatibility. What you can do, and what everyone else does, is use ActionBarSherlock.
Why do we need this third-party lib?
ActionBarSherlock is an extension of the support library designed to facilitate the use of
the action bar design pattern across all versions of Android with a single API.
The benefit of this is:
A lot more users for the app
A stable, tested library at your disposal
http://actionbarsherlock.com/
When you use the standard actionbar, it does this only when there is a lot of space to do this. It will be like this when you are in a landscape phone or a tablet layout.
You cannot force the native actionbar to do this layout always. You can instead use a third party tab layout as a custom view. You can use this library. It is great. https://github.com/astuetz/PagerSlidingTabStrip
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
Since the ActionBar is available only in Android 3.0 and later, what is a good way to implement ActionBar-like widget in earlier sdk versions? I am looking to do this programmatically, if that helps.
I have created a library, ActionBarSherlock, which is extended from the Android Compatibility Library to implement support for the native action bar all the way back to Android 1.6.
The key feature of this library is that it mimics the native action bar of Android 3.0+ and allows you to interact with it and theme it on all version of Android from 1.6 up through the current newest version, 3.1. There are samples and documentation on the website linked above which should give you a good idea about how it works.
You can also look on the implementations page on the GitHub wiki for real world applications of the library.
The Google IO 2011 app is a good example
It runs on versions of Android less than 3.0 as explained during the Google I/O 2011 session, Designing and Implementing Android UIs for Phones and Tablets.
Use android-actionbar or GreenDroid.
The new Android support library adds ActionBar support back to API 7.
http://developer.android.com/tools/support-library/index.html