Skip to main content
Compare

AppBlocks vs. Arduino

Arduino made embedded development approachable for millions of people. AppBlocks is aimed at the next step: taking a device from prototype to a product that installers can configure and you can manage in the field.

Side by side

From sketch to shipped product

How the typical Arduino workflow compares with AppBlocks when you build a connected device.

CapabilityTypical Arduino workflowAppBlocks
Programming modelC++ sketches with setup() and loop()Event-driven flowcharts, generated as Zephyr C
Timing and concurrencyManaged in your own loop codeEvents, timers, and a scheduler as blocks, on an RTOS
Device web interfaceBuilt by hand with a web server libraryGenerated Web Console on every device
Persistent settingsYour own storage and menu codeSettings in non-volatile memory, editable from browser, phone, or cloud
Industrial protocolsCommunity libraries, integrated by handModbus RTU/TCP, MQTT, and HTTP as ready-made blocks
Fleet management and OTAA separate service or your own back endAppBlocks Cloud, built in
Production hardwareDevelopment boards; enclosures and industrial I/O are up to youTibbo modular hardware with I/O modules and enclosures, or other boards

Arduino is a trademark of Arduino SA. This comparison describes the typical Arduino IDE workflow, not every Arduino product.

Which to choose

The right tool for the stage you’re at

Choose AppBlocks when…

  • The device is going to customers or into the field, not just onto your desk
  • You need a web console, installer settings, cloud management, or OTA updates
  • You work with industrial equipment over Modbus, or report to MQTT and HTTP back ends
  • Your team would rather review a flowchart than a large codebase

Choose Arduino when…

  • You’re learning electronics or C++, and want the huge library of tutorials
  • You’re building a one-off prototype or hobby project
  • Your project depends on a specific community library
FAQ

Questions, answered.

Can AppBlocks run on Arduino boards?

AppBlocks targets boards supported by Zephyr RTOS, which include some Arduino boards such as the Nano 33 BLE. See supported boards.

Do I need to know C++ to use AppBlocks?

No. You build your firmware as a flowchart. AppBlocks generates readable Zephyr C code that you can inspect and extend if you want to.

Can I start on a development board and move to production hardware?

Yes. AppBlocks lets you swap hardware without rewriting your application logic, and Tibbo makes modular, production-ready hardware you can order from the Designer.

White-glove onboarding included

Ready to build your first firmware?

Start free in your browser, follow the tutorials, or book a free one-on-one session. No board yet? We’ll demonstrate everything on ours.