Hi everyone,

I’ve been experimenting with my M5Stack device recently and wanted to try something a bit different from the usual IoT or sensor-based projects.

I got inspired by word puzzle games like Letter Boxed, where players connect letters from different sides to form words. It made me curious—could something like this be built on an M5Stack device with its small display and input buttons?

So far, I’m exploring:

Displaying letters dynamically on the screen (possibly rotating sides)
Using buttons or touch input to select letters
Creating a simple logic system to validate word combinations
Keeping the interface minimal due to screen size limitations

I think it could be a fun mix of embedded systems + game logic, but I’m not sure about the best approach moving forward.

A few things I’d love input on:

Would you handle word validation locally or connect to an API over WiFi?
Any tips for optimizing UI on small M5Stack screens?
Has anyone here built a small game not just IoT tools on M5Stack before?

I’ve seen a lot of creative hardware projects here, so I’m curious how far we can push these devices beyond typical use cases.

Looking forward to your ideas and suggestions

Hi everyone,

I’m fairly new to the M5Stack ecosystem and recently started exploring its hardware and development environment. I’ve been really impressed by how modular and beginner-friendly everything seems, especially for IoT and rapid prototyping projects.

Right now, I’m trying to understand the best way to get started with building simple projects. There seem to be multiple development options like Arduino, UIFlow, and MicroPython, and I’m a bit unsure which one is the most efficient for beginners.

I’d love to hear from experienced users here:

What’s the best starting point for someone new?
Any beginner-friendly project ideas you’d recommend?
Common mistakes I should avoid?

Also, if you have any resources, tutorials, or personal experiences to share, that would be really helpful.

Looking forward to learning from this amazing community!

Thanks in advance

Hi,

Thanks for the clarification and heads-up! It’s good to know what’s actually happening with UIFlow 2.0.0. From your post, the key points are:

The UIFlow 2.0.0 firmware preview is only for local testing on hardware via REPL. It is not compatible with the current online UIFLOW platform.
M5Stack seems to be rebuilding the UIFLOW backend, which is why the web interface isn’t working at the moment.
In the meantime, you can still program M5Stack devices using other IDEs like Thonny or Visual Studio Code, so development doesn’t have to completely stop.

It makes sense to avoid duplicate posts about UIFLOW not working, as this will only flood the forum and make it harder for users to find useful updates. Locking repetitive threads will help keep the community organized.

For anyone affected, I’d recommend:

Using Thonny or VS Code with M5Stack libraries for local programming.
Keeping an eye on official M5Stack announcements for updates on UIFLOW 2.0.0.
Using the REPL mode on hardware to test new firmware features safely.

This is a helpful reminder to stay patient while the UIFLOW team rolls out their updates!

Thanks for sharing your findings—this is really useful information, especially for anyone working with ESP32-S3 devices.

The distinction between the two drivers (JTAG/Serial and the low-level modem driver) explains a lot of the issues people run into when trying to reflash firmware. It sounds like the main challenge is getting proper access to Bootloader mode when the second driver isn’t installed correctly.

On Windows and Linux, driver installation can sometimes be tricky depending on permissions or conflicting drivers. It might be worth checking if the correct USB CDC/ACM or WinUSB drivers are being assigned, or trying tools like Zadig on Windows to manually bind the device to the right driver.

Also, holding the BOOT button while connecting (or resetting) the device can sometimes force it into Bootloader mode if it’s not entering automatically.

Good call on warning users about Flipper/Marauder firmware—getting locked out of reflashing can be a real headache. Hopefully, with more testing, a consistent driver setup for Windows/Linux can be identified.

Looking forward to any updates you find!