Smart scenarios
Already, 2,000 Mykuca clients are actively using this section
About product
Mykuca includes a mobile application for cliens of a management company. In mobile app users can submit requests to the management company, manage their smart devices, and stay connected with other residents in the building or complex. Additionally, they can view home cameras, open intercoms, read news from the management company, and participate in surveys.
Task
Design a section in a mobile app where users can set up scenarios for smart devices. These scenarios should trigger based on conditions set by the user. The app will work with a specific set of devices. Also, I needed to design a similar section in the admin panel for engineers.
Competitive analysis
I reviewed the functionality of several smart scenario creation apps. I selected features that fit our technical limitations and analyzed the user experience.
User flow chart
After analyzing the functionality of other apps, I started developing the main logic for the section.
Prototype
Once the logic was finalized, I designed the main screens as wireframes. Afterward, we reviewed and approved them with the developers
The beginning of the smart scnenario creation
First, the user clicks on the '+' button, then gives the scenario a name and selects an necessary icon.
Condition seting
In this section, user configures the conditions under which the scenario will start. It's possible to select the time and/or device. If the specified parameter is triggered on the device, the scenario's action will begin. For example, if the temperature reaches 30°C. Additionally, user can set the conditions to determine if the scenario should start when all conditions are met or if at least one condition is fulfilled.
Action seting
In this section, the user configures a single action or a sequence of actions to be triggered based on specified conditions. The action is a device parameter, such as turning on the air conditioner. The user also has the option to delay an action or insert a pause between actions. Additionally, the scenario can be set to either stop or continue after a device error.
The final scenario screen
At the end, all conditions and actions are added to the scenario screen. Depending on the settings, 'And' or 'Or' will appear in the conditions section. The setting 'All conditions are completed' implies 'And.' If 'At least one condition is completed' is chosen, it will be 'Or.'
Devices llist
The list of devices that could be used in the scenarios was known in advance. The developers and I discussed the functions of each device and planned which ones would be used as conditions and which ones as actions.
Logic of 'Conditions' and 'Actions' Operation
Once the main functionality was defined, we developed the logic for conditions and actions. After extensive discussions, we agreed that in the first iteration, the condition would trigger only if it is less than or greater than (not equal to) the specified number. The action, of course, would output the specified number (e.g., temperature = 24°C).
Sensors
Sensors are predominantly used as conditions. Examples include a door sensor, an air sensor, etc.
Action devices
Devices such as heaters, locks, and blinds are used as conditions.
Admin panel for engineers
The interface was also replicated in the admin panel for the chief engineer, allowing him to create scenarios and demonstrate them to prospective apartment buyers.
Through the admin panel, the engineer can create a scenario for any apartment registered in the system. This scenario will later be displayed in the user's application, where it can be modified by the user. Similarly, conditions and actions can be set, device parameters can be configured, and operation times can be selected. The functionality fully mirrors that of the client’s mobile application.
