Development of the interface part (frontend) in C+LVGL according to the layouts in Figma

It is necessary to implement the application interface according to the layouts in Figma on the LVGL + C stack for Raspberry Pi Zero 2W

What the device is

Raspberry Pi Zero 2W with an installed system image, in which LVGL is already integrated, the standard Raspberry graphical interface is disabled, and there are the following input-output devices:

• 320x480 display (driver integrated)
• touch (integrated into the system, standard driver)
• membrane keyboard (connects via SPI, API\SDK will be provided)
• measurement sensor connected via USB (you will not need to work with it and implement the exchange protocol, we will either work with a sensor simulator or you will simply assume in the code that the data has been received).

What needs to be done

1. Implement the interface from Figma on the device using the LVGL library and the C programming language (implementation of the graphical interface and logic). The interface must be fully functional (all transitions between screens, input and display of values, working with the archive, etc.), but there is no need to work with real data. For example, you implement the "Save" button for measurements, implement the archive interface for saved measurements, while for the save button and when viewing measurements, you simply place stub functions that simulate this; the necessary code will be added later.
2. Communications (wifi, usb, Novotest lab) - at this stage, it is not necessary to fully implement the exchange; it is sufficient to have a fully implemented interface with network/device overview and connection/pairing + software stubs for connecting external libraries and/or launching external applications and/or subsequent implementation of exchange in C\LVGL.
3. Saving measurement results in the device archive (memory) and reading them from the archive (memory) (viewing saved measurements in the device Archive) on the device screen. You only need to implement the interface according to the layouts and leave stubs that simulate writing to disk and reading from disk.
4. Ensure 30 FPS when the interface is running. This is achieved automatically when working on the specified stack, but this requirement needs to be formally stated because there will definitely be those who can make a stable solution stop working stably.

In total, the result of your work is a complete mockup of the device interface according to Figma, with all screens, all transitions between screens, and simulation of value output.

Development result

1. A working application on the LVGL\C stack, with FPS of at least 30.
2. In the application, a fully implemented interface according to Figma (graphics and logic). Measurement, calibration, archive on the device (saving, viewing), device settings - all screens, all transitions between screens, simulation of output of all values.
3. Communications (USB, Wifi), Archive, and other modes where real physical data is required - the interface is fully implemented, you use virtual data + stub functions simulating data reception and transmission.

I do not publish Figma layouts in open access. If you feel capable and, most importantly, have experience implementing something similar on the above-mentioned stack - please send a personal message with a request, I will provide a link and access to view the layouts. It is highly desirable to immediately indicate examples of implementations of something similar in essence or stack or describe your experience in developing something similar in this request.

To understand the interface in principle, I provide several window options (there will be about fifty in total).

Measurement

Archive

Settings