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
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
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 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
i want to my application could run in all of android version and after any research about it i'm find to component about that such as Sherlock and AppCompat whats difference Sherlock and AppCompat? which is best for my application to work all of android version such as Fragment , Actionbar or etc?
Sherlock is Hard to import and use that in Eclipse and Intllij and i can not work simply that.
#TuxWorld, Action bar is a component that adds a bar on top of your application.
Android provides a native implementation as part of SDK which is the "AppCompat" version you are referring to. "Sherlock" is an extension to the native implementation (Before there was a native implementation, Sherlock was the way to add action bar). Sherlock version is an open source library that you will have to add to your project where as SDK is already available for you. For most cases using Actionbar provided by AppCompat would fine. However depends on what you are really trying to achieve.
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
Customize the action bar is not very easy, and if you support the old android versions you need the compatibility library. What are the advantages and disadvantages to use a view instead of the action bar?
Well, if you've made a view that works the same and look the same as the action bar, you've actually implemented the action bar, so why bother doing it instead of just taking the code of it...
Anyway, the action bar is a very well known component over most Android apps, and it's part of the look&feel of them and of the OS itself.
doing things on your own will take a lot of time and effort, and it will have a huge chance of making the users not comfortable with using it (unless you've done something really remarkable and easy to use).
developers can always "invent the wheel" , but most of the times, it's not worth it.
The action bar is an important design element, usually at the top of each screen in an app, that provides a consistent familiar look between Android apps. It is used to provide better user interaction and experience by supporting easy navigation through tabs and drop-down lists. It also provides a space for the app or activity’s identity, thus enabling the user to know their location in the app, and easy access to the actions that can be performed.
use ActionBar instead of a View so you won't reinvent the wheel. It's not hard to customize if you use tools: http://jgilfelt.github.io/android-actionbarstylegenerator/
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
Much importance has been placed on this UI element. And for good reason too, as it provides a standard UI element, for developers and users alike. So, please understand that I do not wish to contest its usefulness.
On Action Bar pattern: (taken from here)
It provides several key functions:
* Makes important actions prominent and accessible in a predictable way
(such as New or Search).
* Supports consistent navigation and view switching within apps.
* Reduces clutter by providing an action overflow for rarely used actions.
* Provides a dedicated space for giving your app an identity.
If you're new to writing Android apps, note that the action bar is one
of the most important design elements you can implement. Following the
guidelines described here will go a long way toward making your app's
interface consistent with the core Android apps.
The question:
Is an Action Bar indispensable? Are there functions that cannot be implemented if one chooses to forgo this pattern (may be in navigation dept.)? Would there be any platform or device specific problems?
It is not mandated in any way by the Android Platform. You can very easily accomplish many of the same things designed to be done in the ActionBar on your own (navigation, context information about your app).
You will not have any programmatic challenges doing these things without using the ActionBar.
However, this component is a very important pattern in the Android OS, so you better have a very good reason to not use it, as your app will not 'fit' in the Android ecosystem, which will be a negative user experience.
Bottom line, there is nothing mandating that you must use the ActionBar, and you can accomplish the same actions in other ways, but this is not suggested, you should use it, so your app looks like it fits in the Android ecosystem.
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.