The user is rewarded with immediate results, with no extraneous criterion entry or navigation. After each “find” the user sees different information that may take them in a completely new direction (hence, pivot). The “pivot” descriptor comes from how a user in discovery mode interacts with a database. Users click/tap on “action” to see the list of movies with that genre, the director’s name to see a list of his films, etc. True to mobile’s minimalist style, users interact by clicking (or tapping) directly on the content the data fields ARE the “buttons” that initiate action. They don’t quite know what they want to see (no specific find criteria) so they will be using the “browsing” links provided to get ideas. The use scenario is a casual user browsing a movie database. exploring a movie database (click image to enlarge) To demonstrate one such solution we used a single global field, OnObjectEnter script triggers, and a couple short scripts.
I also wanted to see if it made sense to use the same UI on the desktop, to provide a more seamless cross-device experience. The general idea was to explore how to streamline complex Finds (that usually are multi-step processes) in a way that was iOS-friendly. To recap, this file shows a UI proof-of-concept using the new button states in FMP12. One of our demo files was featured at the 2012 FileMaker Developer Conference (DevCon), at Bob Shockey’s session “The Design Universe.” During the session folks requested a copy of that file, happily provided here.
0 kommentar(er)
