Tag Info

New answers tagged

0

Use AutoCompleteTextView entries only If you have too much entries for a spinner, this is the best known way currently. An implementation solution is on stackexchange


1

The position of the button depends on the use case and whether or not your toolbar is a global bar or specific to the current view of the app. The left side of the toolbar is typically reserved for actions associated with the current view of the app. In the use case you provided the toolbar is custom to this view of the app (only appears during profile ...


0

In the current context, i think the system should speak what the user can understand without thinking about it. I agree to your apprehension in using the clear icon, it does look like the refresh and it would be unnecessary to use an icon here when text could easily fit in. Here is an interesting thread on what might make it clear for you : Icon vs Icon ...


1

Having the back and next at the bottom interferes with the number/alphanumeric keyboard and material sheets that slides up from the bottom. Use the native android action bar to display consistent navigation and view switches within the app. Use the native "Input Controls" for your "next button" following Googles design standards. Visit google.com/design ...


0

The issue with tabs is the space that you can show them on mobile devices. It's really good if you know that you only have say three items to show, but when it comes to future proofing, there's not enough space to go width wise without paginating. The way in which I see it is the use of tabs should be for the immediate usage in the journey and the draw is ...


1

Yes there are alternatives Since you only have two views, a common approach that is also applicable to Material Design is to provide a toggle icon or word (map or list) in the topbar. This avoids the need to take up valuable real estate with a tab control, and may help you avoid the awkward scrolling design by enabling a fixed topbar. This approach is ...


0

My rule of thumb (which pretty much merges with @DA01's comment), is "Do as much as you can, but don't do more than needed". Maybe, if you wanted to give each platform its different design guidelines to appeal everybody, you could simply make a native app (do as much as you can). They tend to be a better choice for users, rather than accessing a website, ...


1

Forget the "platform wars" and make the application user friendly from a touch perspective. The most important aspect you must try to achieve is to deliver a seamless experience across multiple platforms (make your app look and feel the same as much as you can on all platforms). As I see your application is not a very complicated so that shouldn't be so ...


0

Consider the content to be displayed in the app; you're displaying lists. This means that when thinking about navigation, the most natural way to start is by 'listing' your list choices. Your heirarchy is fine, and the tabs are a good starting point in this case. A good convention when designing for tablets is a vertical bar design, like google uses for ...


0

So here are two very simple solutions: Underlined Phone Number Like @Jamezrp said you could underline the telephone number which would indicate that there is an action behind tapping the telephone number. Phone Number Button Alternatively, you could put the telephone number in a button with the text "Call 00112345" which would be very clear that clicking ...


2

The default is, as you said, to underline it where clicking on it will activate the phone app. Alternate solutions are all graphical-based, using the same mechanism but adding something to the number. Skype has a box around numbers, Google Hangouts puts a circle with an icon, etc. You can spend time doing that, but I recommend first offering the basic ...


0

If you looking for inspiration on Material design apps then I would recommend looking at Material Up which contains tons of Material redesigns of popular apps including social networking apps. You might already know about Material Design Guidelines which will show all the new ideas and concepts behind Material design. Also just because Material provides ...


1

I think what you want to do is within the guidelines and would be an acceptable practice. I have included two examples of what you could do as well as the example that @tehShane provided. Example 1 You could extend the toolbar to include a persistent search bar like the example below. With the new Toolbar widget it is very easy to customise and extend your ...


0

Something as simple as a List might be your best option here. You can do something similar to what @onofre-pouplana has mentioned above in which clicking on a list item will expand the list item to take over the whole screen. Obviously you would want to do some animation to make it look good and to give the user an understanding of what is happening. Below ...


0

@awidgery Personally I think this is more of a technical question but I will try to answer it for you; If your app is an Android app you will be able to use Gradle to switch your app between Production and Development. What you want to take a look at is build types. If your app is an iOS app you should be able to do this using a Configuration File. If you ...


0

I'll totally agree with your co-worker and here I'll explain you why: Inside your Downloads tab you should have just downloaded music. If you want to add also music that has been introduced in the device by other means (usb, sd carc,etc), the "Downloads" tab is not an appropiate title, it's inconsistent. Expandable lists are very close to each other, so ...


1

Would this work for you? Merging the two lines into one, but not sacrificing too much space?



Top 50 recent answers are included