flipperzero-ufbt VS flipperzero-firmware

Sources? No. I don't have an application folder. I use ufbt. (Forgot to write that in the post, sry)

You can build your apps for Flipper in 2 ways: either alongside main firmware, using fbt, or with ufbt. For guides and examples - see the links mentioned by others. And check out stock firmware's components, they are designed exactly the same way as user-created apps runnable from SD card.

For separate applications, better use ufbt https://pypi.org/project/ufbt/ - it's designed to be called from app's folder, is faster and easier.

You can also use ufbt https://pypi.org/project/ufbt/ for building apps outside of firmware repo - and automating application building on GitHub.

You can also use https://github.com/flipperdevices/flipperzero-ufbt for building apps - it's as lightweight as possible and doesn't bring full firmware sources. However, full sources are useful when looking for examples of API usage.

You'll need basic C knowledge. There are official docs on flipper-specific aspects of creating applications. You can also use ufbt to create and build apps outside of full firmware source tree.

You'll need to build those apps using the vanilla firmware. Try using ufbt to build them.

Right now, we already have all the tools you need to build your app and upload it to your Flipper via USB without cloning the firmware, re-flashing it, etc. The tool is called ufbt (https://github.com/flipperdevices/flipperzero-ufbt), and you can use it by creating a new folder for your code, creating the application.fam Manifest (where you define the name and the starting function aka entrypoint for your app), opening up your favorite code editor (we recommend VSCode but you can use any text editor), and writing your program as you would with Arduino (though, using our libraries instead of the incompatible arduino ones).

I'd greatly appreciate if you covered app development with ufbt - https://github.com/flipperdevices/flipperzero-ufbt (or at least mentioned its core features).

Man I got really excited thinking this was about the Flipper Zero device https://flipperzero.one/

We use littlefs in Flipper Zero's firmware[1] for storage in leftover flash space after the main firmware image. Flipper implements a virtual FS, where both external SD card and internal storage have own mount points. SD card is used for storing apps and user-created data, and internal littlefs contains persistent data like BLE pairing, system services configs and such.

We never had any issues with littlefs - however, it cannot be easily repartitioned when amount of available leftover space changes with firmware updates. So on installing an update, it gets fully backed up to SD card, reformatted and later restored.

1- https://github.com/flipperdevices/flipperzero-firmware/blob/...

Issue opened.

It is used in FlipperZero with FreeRTOS to handle the data structure.