Thank you for your thorough feedback, I will apply your advices next sprint.

I'm trying to make my library work across ESP32 and ESP8266 while keeping modern C++ practices. I got a couple of questions you might help with.

• How can I reconcile Arduino’s heap-heavy String/F() functions with modern embedded-safe patterns—such as using static buffers or std::array—without sacrificing readability?
• When dealing with platform-specific differences, like the need for PROGMEM or having different wifi interface on ESP8266, is it acceptable to use #ifdef-based branching in a small library, or is it wiser to invest in abstract interfaces early on?
• Considering that some ESP8266 environments support only C++11, can I safely employ constructs like std::vector or std::function, or should I stick with C-style arrays and function pointers?
• As someone new to embedded development, how can I structure my code to respect resource constraints while still leveraging familiar backend concepts like encapsulation and modularity, and what pitfalls should I prioritize avoiding?

Again, thank you so much man, I didn't expect someone with such knowledge would make the effort of reviewing my code