WEEK 15 — Interface and Application Programming

Group Assignment Checklist

This section documents the group work for the Interface and Application Programming assignment. The objective was to compare as many tool options as possible for creating applications and user interfaces that communicate with embedded microcontroller boards.

• ☑ Compared multiple interface and application programming tools.
• ☑ Compared web, mobile, desktop, IoT dashboard, and SCADA-style options.
• ☑ Identified communication protocols used by different interface tools.
• ☑ Compared tools according to programming language, difficulty, and use case.
• ☑ Related interface tools to embedded boards, inputs, and outputs.
• ☑ Documented the group research process on the group assignment page.

Group Assignment – Tool Comparison

The group assignment for this week asked us to compare as many tool options as possible. Since the topic is Interface and Application Programming, we focused on tools that allow a user to interact with an embedded system.

The tools compared in this page include IoT dashboards, web applications, mobile applications, desktop interfaces, visual programming environments, data visualization platforms, and SCADA-style tools. These tools can be used to display sensor values, send commands, control actuators, monitor machine states, and build dashboards for embedded boards.

What is an Interface?

An interface is the connection layer between a user and a system. In embedded electronics, an interface allows a person to observe data, send commands, change parameters, and understand what the microcontroller is doing.

Interfaces can be simple or complex. A simple interface can be the Arduino Serial Monitor displaying sensor values. A more advanced interface can be a web dashboard, a mobile application, a cloud IoT platform, or an industrial SCADA system.

Automation Pyramid and Interface Levels

Interfaces can be understood through the automation pyramid. At the bottom of the pyramid are the physical devices, such as sensors and actuators. Above them are controllers, such as microcontrollers and PLCs. Higher levels include supervision, dashboards, production systems, and business systems.

In Fab Academy, most interface projects are located in the first levels of the pyramid: field devices, embedded boards, and user dashboards. However, the same ideas can scale to industrial systems where SCADA and HMI tools are used to monitor machines and processes.

Image source: The image w15_1.png was generated with an AI image generation tool.

AI Image Generation Prompt

Create a professional horizontal 16:9 infographic titled “AUTOMATION PYRAMID” showing the levels of industrial and embedded system interfaces, using a dark navy futuristic background with a glowing teal and blue color palette. In the center, design a five-level pyramid with horizontal layers, wider at the bottom, labeled from bottom to top: Level 0 — Field Devices: sensors, switches, motors, valves, LEDs, actuators, with icons of a sensor, motor, valve and LED; Level 1 — Control: microcontrollers, embedded boards, PLCs, with icons of a microcontroller board and PLC modules; Level 2 — Supervision: HMI, SCADA, dashboards, machine monitoring, with monitor icons showing gauges and charts; Level 3 — Operations: MES, production tracking, process coordination, with factory and analytics dashboard icons; Level 4 — Enterprise: ERP, planning, business management, with cloud, building and business growth chart icons. Add a downward arrow on the left with the text “Commands & control flow downward” and an upward arrow on the right with the text “Data & information flow upward”. At the bottom, include a highlighted note box saying “In Fab Academy projects, most work happens between Levels 0, 1, and 2.” Use clean white typography, modern technical line icons, thin glowing lines, strong visual hierarchy, and a polished educational presentation style suitable for a Fab Academy documentation page.

Types of Interfaces for Embedded Systems

Different projects require different types of interfaces. A small prototype may only need a Serial Monitor, while a connected IoT device may need a mobile or web dashboard. A machine or industrial process may need a SCADA-style interface with alarms, historical data, and multiple screens.

Image source: The image w15_2.png was generated with an AI image generation tool.

AI Image Generation Prompt

Create a professional horizontal 16:9 infographic titled “INTERFACE TYPES” with the subtitle “Main interface categories for embedded systems and IoT projects,” using a dark navy futuristic background, glowing teal and blue accents, clean white typography, thin neon borders, and modern technical line icons. Design six rounded rectangular cards arranged in a 2-column by 3-row grid, each card numbered and labeled: 1 — Serial Interface, with an icon of a terminal window and USB cable, text “Arduino Serial Monitor” and “Debugging and quick tests”. 2 — Desktop Interface, with a computer monitor icon, text “Processing, Python, PyQt” and “Local computer control”. 3 — Web Interface, with browser, globe and code icons, text “HTML, CSS, JavaScript” and “Browser-based dashboards”. 4 — Mobile Interface, with smartphone and touch hand icon, text “MIT App Inventor, Flutter” and “Phone-based interaction”. 5 — IoT Dashboard, with cloud, device, gauge and database icons, text “Blynk, ThingsBoard” and “Cloud monitoring and control”. 6 — SCADA / HMI, with industrial dashboard and factory icons, text “Industrial supervision” and “Machine monitoring and alarms”. At the bottom, add a highlighted note box saying “Choose the interface according to the project: local, mobile, web, cloud, or industrial.” Also add a small “Typical use” strip with icons and labels for “visualize data,” “send commands,” “monitor outputs,” and “control actuators.” Make the layout polished, high-impact, readable, educational, and suitable for a Fab Academy documentation page.

Communication Protocols for Interfaces

An interface needs a communication method to exchange information with the embedded board. Some protocols are local and wired, while others are wireless or cloud-based. The correct choice depends on distance, speed, power consumption, complexity, and whether the system needs internet access.

Tool Categories Compared

The group organized the tools into categories according to how they are used. Some tools are designed for beginners and fast prototypes, while others are better for custom interfaces, industrial systems, or large IoT deployments.

Image source: The image w15_3.png was generated with an AI image generation tool.

AI Image Generation Prompt

Create a professional horizontal infographic titled “INTERFACE & APPLICATION TOOLS COMPARISON” with the subtitle “Tools for Embedded Systems, IoT, Dashboards, Mobile and SCADA Applications,” using a clean white background, dark blue frame, modern typography, thin section borders, and a polished technical presentation style. Organize the infographic into clearly separated panels and columns with colored section headers, each one comparing categories of tools commonly used in embedded systems and Fab Academy style projects. Include these main sections: 1. IoT Dashboard Platforms Show tools such as Blynk, Arduino IoT Cloud, ThingsBoard, Ubidots, and Adafruit IO, each with logo/icon, name, and a short one-line description of its purpose. 2. Low-Code & Visual Tools Show Node-RED, MIT App Inventor, Thunkable, and AppSheet, each with logo/icon, name, and a short one-line description. 3. Web & Custom Development Show HTML / CSS / JavaScript, Flask, FastAPI, and p5.js, each with icon or logo, name, and a concise description. 4. Desktop Applications Show Processing, Python Tkinter, and PyQt, each with icon or logo, name, and a concise description. 5. Data Visualization & Analytics Show Grafana, InfluxDB, Google Data Studio, and Power BI, each with icon or logo, name, and a concise description. 6. SCADA & Industrial HMI Show Ignition, OpenPLC HMI, and Node-RED Dashboard, each with icon or logo, name, and a concise description. 7. Communication Protocols Split this area into Wired and Wireless & Network categories. Under Wired include Serial / UART, I2C, SPI, and Modbus (RTU/TCP). Under Wireless & Network include WiFi, Bluetooth / BLE, MQTT, HTTP / HTTPS, WebSocket, and OPC UA. Each protocol should have a small icon and a short explanation. 8. Tool Comparison Summary Create a comparison table with columns such as: Tool, Interface Type, Web, Mobile, Programming Level, Protocols, Best For. Include rows for Blynk, Node-RED, ThingsBoard, Grafana, MIT App Inventor, Processing, Flask / FastAPI, and Ignition (SCADA). Use check marks, crosses, and short text labels where appropriate. At the bottom, add a note strip that says: “Choose the right tool according to your project needs:” and include small labeled criteria such as: Type of interface, Programming knowledge, Communication protocol, Real-time data, Historical data, Control outputs, and Scalability requirements. Add a small legend in one corner indicating: Beginner Friendly, Medium Level, and Advanced / Industrial. Make the infographic visually balanced, highly readable, educational, detailed, and professional, suitable for a Fab Academy or engineering documentation page.

Main Tool Comparison

The following table compares different tools that can be used to create interfaces for embedded boards. The comparison considers the type of interface, whether it supports web or mobile use, the programming language or logic used, typical protocols, difficulty, and recommended use.

IoT Dashboard Tools

IoT dashboard tools are useful when the embedded board needs to communicate through the internet. They are especially suitable for ESP32-based boards because these boards can connect to WiFi and send sensor data to a cloud service.

Low-code and Visual Programming Tools

Low-code tools are useful when the goal is to build an interface or automation workflow quickly. Instead of writing everything from zero, the user connects blocks, nodes, or visual elements.

Custom Web and Desktop Interfaces

Custom programming tools give more flexibility than low-code platforms. They require more development time, but they allow the designer to control the interface layout, behavior, communication, and data structure.

Data Dashboards and SCADA-style Tools

Some tools are focused on data visualization and process supervision. These are useful when the system needs historical charts, alarms, machine states, database connections, or industrial communication protocols.

Recommended Tools by Scenario

The best tool depends on the goal of the interface. A tool that is excellent for a small Fab Academy prototype may not be the best option for an industrial machine, and a SCADA system may be too complex for a simple LED or sensor demo.

Selection Criteria

To compare interface tools, the group considered several criteria. These criteria help decide which tool is more appropriate for a specific project.

Group Comparison Notes

During the comparison, we observed that interface tools can be selected according to the complexity and purpose of the project. For simple Fab Academy prototypes, tools like Blynk, Processing, Node-RED, MIT App Inventor, and Python interfaces can be implemented quickly. For larger IoT projects, platforms such as ThingsBoard, Arduino IoT Cloud, Ubidots, or Adafruit IO provide dashboards and device communication tools.

For projects that require historical data, Grafana with a time-series database is a stronger option. For industrial or machine supervision, SCADA and HMI tools are more appropriate because they are designed for process visualization, alarms, machine states, and production environments.

Summary Table

The table below summarizes the most relevant tools for Fab Academy interface projects.