Before designing the interface, it was essential to understand what the system is to its users instead of how the designers present it. This was carried out by creating conceptual models, namely by the definition of a system metaphor ^[1]. The principles beneath this approach relate to the definition of analogies with the real world; the definition and relation between concepts correctly mapped to the task domain supported by the system. Therefore, in the context of the work presented in this paper, it was crucial to understand what meal planning is for users.

Conceptually, meal planning includes types and amounts of food, incorporating dietary fiber, understanding proper serving sizes, management of eating out and special occasions, as well as incorporating favorite recipes. In real terms, meal planning relates to different food types in a dish. Meals are different throughout the day; the major understood types are breakfast, lunch, snack, and dinner. With this in mind, and considering knowledge acquired by users throughout their lives, a metaphor for the system is the Plate Model ^[2], as presented in Figure 1. It is a visual method of food representation through pictures, graphs, charts, and food replicas. The centerpiece is the dinner plate, which serves as a pie chart representing the proportions of food. The model also includes side dishes, beverages, and other meal courses. One of the critical elements in nutrition is learning appropriate food quantities. To this end, portion size is an essential aspect of the plate model. Each food must be visually represented in the correct size concerning the overall food distribution on the plate. Using the plate model allows users to understand the concept and carry out tasks in an interface as in real life.

The metaphor used in this context imposes two significant constraints: the creation of sections in the dish—where food is placed—and the visual representation of food so that users will understand the meal. For the first, as presented in Figure 2, the general idea is to create sections in the dish that contain food (considering the food plan prescribed by a nutritionist). The algorithm used to create the circular areas is presented.

For the visual representation of food products, a list of 1307 products was considered. Given the effort required to create each item, they were separated into 77 categories representing several food products or groups. Similar categories were grouped into contexts: drinks, common carbohydrates, milk derivatives, deserts and sweet food, proteins, fruits, vegetables, and other categories that do not fit in the previous. All the elements were created in the scope of this paper for an accurate representation of the food products.

Another important aspect is the percentage of food ingested from the dish. The real-time monitoring of a food plan depends on the feedback on the adequate ingestion of nutrients. It avoids misleading feedback on meal consumption. Therefore, it is critical to represent the percentage of consumed food, which is concordant with the common knowledge of users and the plate model, instead of looking at grams of consumption, which are much more challenging to measure. This way, visual markers were created, representing 200%, 150%, 100%, 75%, 50%, and 25% of each food in the prescribed meal.

Several requirements have to be met so that the application can be used by both AP (at an early stage of AD) and IC/FC. Therefore, this section aims to provide a tool to control a nutritionist’s real consumption of a prescribed food plan and the development of several components. First, the core component of the application is the dynamic import and presentation of the meal consultation and the consumption of food in a meal. It comprises a meal tab, a detailed view of the food that composes the meal, and the plate presentation and the food on the plate, as presented in Figure 3.

Given that dehydration is common in people with diseases that cause dementia, water intake outside meals is a critical aspect to consider for patients and has to be taken into account in the interface design and implementation. In the following subsections, several features of the application are presented. 

In a food plan, the nutritionist defines the meal and it is delivered to the patient or its IC. Every imported meal is dynamic and can be composed of a combination of soup, main dish, water, and desert (Figure 4). Each element contains different food consumed (or not) by the AD patient. These data are stored in a structure containing Boolean values determining the element’s visibility in the dish tab.

Moreover, when a user consumes a dish, this list provides feedback to the user on the meal consumed. To achieve that, the data structure containing the food in the dish is compared to the food consumed. A checkmark is added to the meal to represent its consumption when there is a complete match.

Another important feature is the food placement in the dish when the food plan is imported. The D3.js (Data-Driven Documents) ^[3] provides a set of libraries that allow data to bind to a Document Object Model (DOM). Reseasrchers implemented a variation of the Zoomable Circle Packing library ^[4], where a circle represents each node (meal). All children of that node (food in a meal) are positioned next to each other at that level, as presented in Figure 2. This library determines the size and minor circle spaces considering the amount of food to be ingested (in grams). It allows the correct representation of food for a natural and dynamic visualization of meals to the user, depicted in Figure 5.

Another important feature is the correct representation of food in a meal when the food plan is imported into the application. Visually, if a certain amount of prescribed food is low, then the visual representation of this food in the dish must be low (as in a normal dish). For example, if broccoli has a low percentage in the dish, its size has to be adjusted to be visually adequate. To implement relative amounts of food in the dish, the flow presented in Figure 76 was applied.

The logic is implemented in the following manner. First, it is important to consider that a food plan is composed of the amount of food (in grams) that must be consumed to reach the goal of nutrients for each day. Therefore, the amount of food is converted into the percentage of food occupied in a dish. Next, the percentage of food is converted into images representing that food, and a meal is visually generated. For example, if 100 g of a specific food is represented by one image, 200 g is represented by two images of that food.

The previous knowledge of a future meal is of major interest to users once they can plan and anticipate food ingestion. Considering that people tend to shop for food on a weekly basis, the interface design focused on presenting the food plan for a week. This allows users to view the nutrients required for ingestion and change some food that is of interest. The weekly view of the food plan is presented in Figure 7.

For each day, the food plan is presented to the user as a general view of the meals to be consumed. Moreover, the user can add an extra meal by clicking the “+” button (see Figure  8). When a portion of food is consumed (food with a checkmark in Figure 6), the nutrients associated with the food are added to the overall nutrients that are to be consumed on a specific day. So far, the natural operation of viewing and the general consumption of a food plan was created in the interface and is presented. The following sections focus on the design of the remaining four natural operations on food in a meal: partial consumption, exchange, add/remove, and water consumption.

The concept associated with partial food consumption in a meal is very important for nutritionists since it determines the number of nutrients consumed according to a prescribed food plan. Therefore, if a user only consumes 80% of a particular food, it is important to provide such feedback to the nutritionist since this will provide a realistic view of the food plan consumption and infer the real amount of nutrients consumed. This is presented in the first row of Figure 9, where the user registers the consumption of only 90% of the defined amount of carrots.

The concept of food change in a meal is associated with the ability of the user to change food from the food plan (with an equivalent) related to the user’s food preferences and the availability of specific food. This allows users to adjust the food plan, maintaining the base nutrients that compose a meal (second row of Figure 9, where a soup is changed with another soup). To this end, the user interface was created considering that food equivalent to the same nutritional level can be exchanged with another food.

Finally, adding food to a meal is an option that has to be provided to users. Consuming food outside a prescribed food plan is not a desirable option since the plan is adjusted to nutrients for each user. However, adding this feature allows positive feedback to the nutritionist and implements a realistic view of ingested food (Figure 8). Moreover, it allows the nutritionist to adjust periods of food ingestion and types of meals by considering the user’s food ingestion habits.

Water consumption is most important to individuals with Alzheimer’s due to the impact of a lack of hydration. Therefore, this element, presented in Figure 10, is represented in the meal interface and the menu tab. The design process is analogous to the mental, where the user has visual markers for water ingestion and different quantities of water. The information on each day’s hydration goal is present since it is a stimulus for reaching the goal and maintaining adequate hydration levels.

Similar to hydration, daily statistics related to the ingestion of macronutrients are also available for consultation (Figure 11). More than a piece of information for consultation, these statistics also serve the purpose of goal-reaching either for the correct ingestion of macronutrients, materialized in calories, or the food that has most contributed to each category.