These content objects can often fill multiple screens, and you can switch between screens. Plus, the desktop app doesn't do a great job of navigating. The user must at least enter the subclass list interface to find a so-called global navigation, and when you drill down to the content level, you will find that this navigation can only help you get back whatsapp Database to the top-level main class list interface. In addition, the lack of necessary contextual indication in the content layer makes it difficult for users to find out which subclass the current content object belongs to. When you are actually experiencing these processes, remember to record your observations and thoughts in a timely manner. These records may play an important guiding role in the creation whatsapp Database of interaction models. As we learned in the list modeling exercise, some seemingly innocuous sporadic ideas can be expanded into valuable interactive concepts. In some cases, you can add ideas derived from observation records to the interaction model document.
According to the actual situation of the current case, you have made a special record and analysis of the content hierarchy in a targeted manner; this information will have a decisive impact on the construction plan of the interaction model. At present, our understanding whatsapp Database the content structure is roughly like this Content structure in X company desktop application There is a serious problem with the interaction model of desktop applications. As we learned in the previous article, when the user is at the content level, he must first navigate back to the main class list interface through the global navigation before entering the subclass list interface whatsapp Database or the content object list interface in a subclass again. And this is just one of many problems. It's not clear to you whether this mesh model in desktop applications can be adapted to the iPhone's user experience model.
Now that we have built a mesh model in the previous exercise, let's try to reuse the concept and apply the interaction mechanism we defined earlier to the information structure of the current case. In the mesh model, navigating from the main class whatsapp Database list interface to the subclass list interface With almost the same grid structure, this interaction model is very similar in experience to Company X's desktop application. This is a good thing for those users who are already familiar with desktop applications. However, after all, this model is still very limited in whatsapp Database space in small screen devices. In the iPhone, we can only use a grid of 3 rows and 3 columns at most, while in desktop applications, the grid can reach 10 rows and 15 columns, and the specific number of columns will vary with the specifications of the display.