Tag Info

New answers tagged

0

A few suggestions from my end: While the device is running For this device when awake For this working device While the device is on You can shuffle between the words "working",'running','not in sleep','not in flight' and the like to go about your phrasing.


0

In my experience, reading the Android documentation is a good first step. Emulators work well but you really want to get comfortable with the design patterns and interactions from an OS level. If you or your company have test devices I would suggest using an Android phone for a few weeks. I used Android for everything excepts calls/texts. You'll start to ...


1

Even though I am not sure whether your questions are entirely UX related, I've done a few Google searches and found the following information, to answer your first question: 1) This is all updated for Android 'L'. Everything about metrics and keylines (sizes etc) http://www.google.com/design/spec/layout/metrics-and-keylines.html Everything about ...


-1

If the user answers "No, thanks", I will not show the dialog and ask again. As from the user's point of view, he already refused to rate the app.


0

If you consider the Google Design Guidelines overhere: http://www.google.com/design/spec/components/tabs.html#tabs-content You can find Tabs, this could be a solution when you have a tab for all floors, and then tabs for floor 1, floor 2, etc. Though, I hope it is not for a sky scraper. In addition, if you want to stick to the Google Design Guidelines you ...


-1

There are statistics. I usually say that there are 4 key points: Ask at the right moment: people are highly willing to rate you if you ask them right after they do some great achievement. Finish one level, gain some points, etc. Ask the right question: wording is really important. Make your question/answer sound like it's part of the game instead of "Would ...


0

I believe in this case the arrow down is a signifier that gives the user 2 pieces of information: "Hey, there's more content" "Ah, and that content will appear below here" In my opinion, the arrow down is in this case more accurate than an arrow right because it shows where the new content will actually be displayed (i.e., below). The arrow up is again ...


1

From my perspective, your UI is good to go. Also yes, user will get idea of swipe to left to see other categories in your app. Also I would like to give u suggestion for some marked place in below screenShot as follow:- Change black colour rather use light shady colour as I seeing your screenshot it seems that your festival(culture event) is a colourful ...


1

You could provide a left to right swipe for single row deletion and on other hand you could provide a right to left swipe in which you could show check box for selection leading to multiple row deletion. This is a unique design as so far I have not seen this anywhere and from UI perspective it will look good. Also in UITableView already have left to right ...


1

For iOS app you could use following library :- colorpicker InfColorPicker NKO-Color-Picker-View-iOS And many more you could find out on github or google itself, and difference could be the feature they provide so it depend's on what you looking for.


1

I put a white border around the unclickable area and the darker border around just the clickable area - feels like this works better... The other option might be to make the background colour of the 'untappable' area the same as the page background, i.e., white.


-1

I will suggest to get the screen width and height dynamically using simple height and width getting parameters. Following is the code to do so, DisplayMetrics displaymetrics = new DisplayMetrics(); getWindowManager().getDefaultDisplay().getMetrics(displaymetrics); int height = displaymetrics.heightPixels; int wwidth = ...



Top 50 recent answers are included