Friday, May 12, 2017

design patterns - Problem with avoiding right caret on Android


I am currently adapting an Android app to follow the design guidelines more and more.


One thing I am doing is removing the right carets as suggested. While this works fine for listview where each row is clickable, I have a bunch of views that display a lot of data in a list-sort kind of layout and only some of them trigger actions like downloading a document, going to a details screen or watching a video. At the moment I am indicating that these rows have an action with a right caret.


It seems like there are no patterns for more complex screen designs like this. Any suggestions on what do to?


E.g in the screen below if there is the right caret on the Order Items line you can navigate to an additional screen. Same for the Order Status screen - in some circumstances you can view more information about the order and then the right caret becomes visible..


Example Screen


I could replace the right caret icon with more specific icons for each use case, but for example for going to a detail screen the right caret seems perfectly fine.



Answer



+1 to both Vitaly and Paul's answers. I would also mention that if a list item has a secondary action, one option is to supply a full-height icon button (not visually a button per se just a touchable region) with a separator to indicate the action. Another option is to expose contextual actions using the contextual action bar (CAB), triggered on long press.



Additionally, in your screenshot I'd recommend removing the extra rounded rectangles around list items (we should add this to the Pure Android section of Android Design). If you need to group items, consider using header rows instead.


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...