Libraries &
developer tools.
These are repository development assets. Check the relevant component documentation before choosing a dependency or hardware profile. There is no combined production-support or licensing offer.
AlSayadLib
Reusable ESP32 development modulesA collection of modules for displays, DHT11 and analog-light sensors, measurement data, Wi-Fi transport, HTTP, history storage and other embedded tasks. It also includes older Wi-Fi, MQTT, device and storage code whose readiness needs individual review.
The practical value is reuse: build on a named component instead of re-creating every small piece of a project. Presence in the library is not a claim that every module is equally mature or tested.
AsDisplay
Display component within AlSayadLibA single-display ESP-IDF component for CYD-style boards, with ILI9341/ST7789 configuration, XPT2046 touch, backlight handling, LVGL integration and simple widgets. C and C++ interfaces are documented.
AlSayad Studio bundles AsDisplay and pinned dependencies for its generated display firmware. That firmware has compilation evidence on Windows and Apple Silicon. Studio’s generated display workflow still needs an accepted board test; a library feature is not automatically a Studio editor feature.
For example, the library supports more widget types than Studio’s current labels-and-buttons screen designer. Choose the correct panel and board settings instead of assuming all CYD variants are interchangeable.
AlSayadEmbedded
Library-only · Physical board revision unverifiedA library-oriented ESP-IDF area for the ESP32-2432S028R family, including independent storage and board-I/O components. Its documentation describes a separate display path and configurable hardware assumptions.
It is not a downloadable end-user application. Integrators need to verify pins, display controller, touch calibration and the actual board revision. Avoid combining display components that both own the same panel or SPI resources.
Studio Extension SDK
Declarative packages · Direct sharingThe current SDK documents a manifest, JSON schema and a sample package for example projects and guided lessons. Packages contain data and license texts; they do not contribute executable code, custom editors, generators or new board definitions.
Studio’s developer tooling checks a package folder and signs packages with a developer key kept in the OS credential store. Another person must explicitly trust that key before installing a directly shared developer package.
There is no public catalog, publisher review program or paid third-party marketplace yet. Directly shared developer packages are not reviewed by AlSayad.
Repository links require the repository to be accessible to the visitor. The local website documentation records the exact reviewed source paths.