I have one doubt, regarding the header navigation control. So my question is instead of having a normal/default title bar , my app should have a customized header view that should be placed at the parent (Top Position) of my screens and it(header) should have some options to be displayed in a horizontal view and those options should be reacting to the events and my inner view should navigate according to the select events
Is it possible to bring my thoughts live. Since i have seen this design and functionality in an android application, i am keen to know to do the same. So please let me know the details regarding the same,, if anybody knows.. Any help will be much thankful
Thanks in Advance...
I am guessing you are talking about something similar to the facebook or the twitter action bar. You could give this link a look. It is Google's own app Iosched and implements an action bar kinda similar to what you need. Use SVN to download the app source, play with it and implement your own.
http://code.google.com/p/iosched/source/checkout
P.S. You would also want to choose a few answers occasionally to increase your acceptance rate. Out of 29 questions you have asked, you have an acceptance rate of 25%. Defeats the whole purpose of Stack Overflow. ;)
Related
In my android application, I would like to show small introductory tips for different features but I don’t want to be intrusive by showing them dialogs. What I want is something similar to:
Sorry for poor design but I hope it’s clear to understand. I want a small bar beneath ActionBar/Toolbar which shows the desired text and a close button aligned right. Clicking this cross button will permanently hide the tip.
Is there some library exists for such purpose or there’s room for something like this?
This will be much better way for applications to express their features without being intrusive.
Well, you can use a modified SnackBar like this
I'm developing a material design app. I want to know that can I add settings option in a Floating Action Button?
Like when user press the button (FAB), settings will be opened. Would this be a good user experience?
I know this question is framed quiet badly, but I didn't find a better way.
Please cooperate.
Thanks in advance.
I won't recommend that. According to Google guidelines, Settings can be shown in the following ways(Please refer the url) https://www.google.com/design/spec/patterns/settings.html#settings-grouping-settings.
And FAB is used for a promoted action. By promoted action means, an action of more priority, which eases a most used action(say, 'Compose' in Gmail).(Please refer this url)
https://www.google.co.in/design/spec/components/buttons-floating-action-button.html#buttons-floating-action-button-floating-action-button
And, of course you can decide where to keep these sort of thing. Ultimately you are the owner of your app :). But these guidelines are good to follow since it will meet a common user's expectation. Ultimately, UX matters ... :)
I want to create a app widget in my desktop and let it support full screen and webview, but I can't find any solution Click Here:
So I am wondering whether there is a way to let app widget support full screen and webview?Or it's designed to not support such function?
I don't think it worth any down vote , in a company , do my best to meet product's requirements should be down vote???? I know it's a very strange question , but I just need others to tell me I can't do this not because I don't have enough skill！Even the official documentation tell me it's almost impossible , but I still ask in Stack Overflow, I don't want to give it up so quick.
Widget has to be placed on launcher and therefore cannot be full screen. If you absolutely need one, implementing your own launcher that can add full screen widget to it may works (I haven't tried this). You probably cannot hide notification bar with it though.
Unfortunately, widget does not support webview according to the documation.
I am relatively new to android development and I'm having a good time so far. My application is functional and I'm ready to add a few options for the user. There seems to be a wealth of information on the ways to do this and I'm having trouble sorting through it and determining which way is the current "accepted" method of providing options to the user.
Does anyone have a great resource to share?
It really depends on the particular app, existing UX, branding and a ton of other design considerations.
In general, starting from scratch, a good starting point (though not universally!) would be the action bar. It gives the user access to ways of manipulating the data on screen, as well as a way of consistently presenting secondary functionality (the overflow menu). Design docs, implementation docs.
I would heartily recommend going through the Patterns section of the design documentation, as it explains the rationale behind many of the core design decisions.
P.S. The reason I'm eager to underline that it's not universal is apps with established UX and user expectations. Examples include Facebook, Path, Google Maps. They all have their reasons for not sticking strictly to the action bar paradigms but they work with it as much as they can.
This Menu Doc page is particularly helpful. But basically if it is API < 11 then you use the hard menu button for an options menu. After 10 the menu items will show in either the ActionBar as action items or in the overflow button. But can still be located in a hard menu button if one exists.
You also always have the option of a contextual menu, primarily with a long click, for things like certain menus depending on the View that is triggered. So maybe show an edit, delete, save menu for a list item.
I should begin by saying that I'm brand new to android development, although I have a good understanding of the fundamentals of java. That being said, I usually learn best by doing, so I'm writing an app for a campus magazine I work for and trying to learn through the process of making it.
At the top of the screen is a bar with two spinners labeled "issues" and "sections," which allow the user to filter the articles shown to only those in the respective issue / section. The rest of the screen is taken up by what I will describe as a vertically-oriented gallery, which shows the headline for each story underneath an image associated with it. The user can then "flip" through the stories in the magazine by scrolling through the "gallery." Selecting one of the stories will open the full story up in ViewPager.
I have two main questions at this point:
1) Initially, I planned to place the "issues" and "sections" spinners in the ActionBar. However, as I understand it, ActionBars are not displayed to users using Android 2.x. Given that these elements are critical to navigating the app, and that a majority of android users are still using 2.x, this seems unacceptable. As a result, I'm using an ActionBar-less theme and essentially drawing my own action bar via a linear layout on top of my main activity. Am I correct in my understanding that ActionBars do not display on Android 2.x devices? If so, am I correct in including my "tool bar" as a part of the main activity, or is there a better way to implement it? (Perhaps as a fragment? I don't really understand how those fit in yet...).
2) I am aware that the gallery widget is deprecated, so obviously I'm not going to use it. What alternative widgets would best achieve the same visual goal of having the user "flip" through the stories in the magazine by scrolling through the widget? Is there a way to animate a ListView to achieve this goal?
Again, any help - particularly which helps me to understand the wider issues involved here - will be greatly appreciated.
Thanks in advance.
You can use ActionBarSherlock - it is compatible down to Android v 1.6.
ViewPager might help you