Fiori Makers Club Showcase 5 Review. Kai Richter, SAP

Transcription

1 Fiori Makers Club Showcase 5 Review Kai Richter, SAP

2 Why did we chose this app as showcase? Beautiful small app with a clearly defined use case. Well-designed following most of our guidelines. 2

3 3 Select Category (1) Using hierarchies in the split app results in empty page on tablet or desktop (2) We recommend not using upper case for readability (3) The number of items should be displayed everywhere. (4) If there is no action, the toolbar shouldn t be shown. 4 We don t use the Split App anymore. 3

4 Select Order 2 1 (1) On this level, you could already select an item to avoid showing the empty page (2) Status not needed here, all the same. 4 3 (3) The tracking number. If there are multiple they should be displayed differently. (4) Consistent labelling 4

5 Order Details - Parcels 1 (1) Order number in title is redundant. We use Orders (123) and Order for title. 2 (2) This is an object view but looks also similar to an object page. Recommendation to use Object Page 5

6 Order Details (Cont.) 1 (1) We try to repeat the data from the list in the details 2 (2) If usually we have only parcel, why plural? Counter? 3 4 (3) The toolbar is only visible on this tab. Footer toolbar are page actions. Action only possible on selection disabled? Position? (4) Button order 6

7 Accepting or Rejecting a Parcel 1 (1) This case should be avoided by disabling the actions (2) Message text and title. Format of select. (3) Button order 2 3 7

8 Order Details - Items (1) We try to repeat the data from the list in the details 1 (2) If usually we have only parcel, why plural? Counter? (3) The toolbar is only visible on this tab. Footer toolbar are page actions. Action only possible on selection disabled? Position? (4) Button order 8

9 Order Details - Printout (1) Printout in fact is a fix list of actions to create receipts use action instead? 1 9

10 Alternative Options

11 Split App Initial State On Tablet We don t use the split app anymore. Would it make sense to add an All category? Could add icons to the categories Search 11

12 The Flow on Phone 12

13 Split App - Parcel Proper use of the Object View with attributes and status. Tabs only for Parcel and Items. Add counters. Use page toolbar for action to create printouts. Slightly different list design using object header control. Actions in list toolbar. 13

14 Split App - Items Using slightly different list layout for items. Proper use of footer toolbar 14

15 Split App One Category If there is only one item type the status is not required. 15

16 Flexible Column Layout Use of full-screen home page and then responsive drill into flexible column layout. 16

17 Flexible Column Layout Master Detail After the home page the master-detail could also be directly opened using FCL. We could use tags to highlight tracking numbers. For details we could use the object page. All information on one longscrolling page. Accept and reject per item. Display status after action. 17

18 Tabbed List Page If the user wants to scan through different lists and have only little navigation we could also use a list page with tabs per category. The list item design could be more visual. 18

19 Tabbed List Page - Popover The action could be on the tag. Maybe not discoverable enough? Instead of tag we could also use buttons. The popover contains the all information about the parcel including the actions. 19

20 Summary Simple app, well designed. Many alternative options to play around with. This would be the basis for further validations. 20