At the core, any UI design should be based on how the minds percieve, learn and act and there are no rules written in stone. Therefore, an effective UX should be designed with the right principles in mind.
It is a well known fact in socialogy, political science and advertising industry that framing perspective organizes experience and guide action. Frames are organizing principles that are socially shared and persistent over time, and that work symbolically to meaningfully structure the social world. As Murray Edelman writes: "The social world is a kaleidoscope of potential realities, which can be readily evoked by altering the ways in which observations are framed and categorized.".
Each digital product can be thought of as a narratives and interpretation which by focusing on one aspect of an event and presenting it to the user it constructs reality. This construction operates by making certain aspects of events more salient than others. This salience then ÏŸÁ ÏŸá ÏŸÁ Ï±ÁÐ™ÏŸÏŽÏ áƒ¢framesÏŸÁ ÏŸá ÏŸÁ Ï±ÁÐ™ÏŸÏŽÏ Ð™ an event and provides a reference point for users in which all subsequent information is judged upon.
The Hybrid app does not neccessarily need to conform to the hosting app (that would be very diffcult considering the varierty of hosts). What is more important is to have internal consistency whithin its own frame (meaning everything looks perfectly measures and polished, etc.). When that happens the psychological effect is 'dazzle' and 'shine'. It will appears shiny and cleaning. every pixel matters* in the sense that as soon as one pixel is off, the overall picture will not look shiny.Non intrusive method for capturing users's attension. Once the focus is on the hybrid app, they wont see* the hosting app
Should not change when scrolling, because scrolling is percieved to be related to the hosting app. The toolbar staying at the top will create the perception that the toolbar is part of the frame*. In other words, to achieve consistency and the cognitive effect, it should visually be percieved to be an extension of the master frame for the hosting app (i.e. the browser).
Human perception is highly affected by the expectations. (we percieve what we want and expect) and we are pattern seeking individuals. The factors that define this are of course the past experiences (which is defined by the target audience) but also the context and the goals.
- Proximity- Similarity
- Continuity- Closure: The mind tends to integrate pieces into a whole object (reference from the Slights of Mind)
Mental focus: Defined by context and goals. The mind will not notice things that are unrelated to its focus point. So even though things are there the mind may not neccessarily see* them.
The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
Users should not have to wonder whether different words, situations, or actions mean the same thing. The particular challenge with the hybrid apps is that the user is faced with conflicting UI paradigms of the hosting app and the hybrid app:
The solution: the UX for the hybrid app needs to be percieved as an extension of the frame for the hosting app. In the case of the hosting app being a web page, the hybrid app should look like an extension of the browser.
(Read full article on preventing user errors.)
(Read full article on recognition vs. recall in UX.)
Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
The best way to design grids that allow create, edit and delete on their items is to:
Some designs try to modify the grid state inline and skip the refreshing of grid with DB call. That argument is bogus because the maximum benefit one might get by avoiding refresh would be the total number of visible grid items which in comparison with big data (which is where performance might become an issue) is negligible. Most designers fall into this trap because they want to preserve the current position on the grid, which our solution fixes.
Are solution would demand:
frame support back item* (i.e. what was the last path/state it came from i.e. /grid/)