V0.7 Release Plan

[Lzw655]

Warning

Since the core functionality restructuring of the System and App components still requires research and design, the development of version 0.7 for the relevant components will be temporarily pending.

Utility Components

• brookesia_lib_utils

---

Service Components [Done]

• brookesia_service_manager
• brookesia_service_helper
• brookesia_service_wifi
• brookesia_service_nvs
• brookesia_service_sntp
• brookesia_service_audio

---

Agent Components [Done]

• brookesia_agent_manager
• brookesia_agent_helper
• brookesia_agent_coze
• brookesia_agent_openai
• brookesia_agent_xiaozhi

Expression Components [Done]

• brookesia_expression_emote

---

System Components [Pending]

• brookesia_system_core
• brookesia_system_phone
• brookesia_system_speaker

---

App Components [Pending]

• brookesia_app_settings
• brookesia_app_music_player

---

Products [Pending]

• phone
• speaker

[csvke]

@Lzw655 you once mentioned about some kind of board support profile (sorry I can't remember how you name it)
Will that be included in the v0.7 release?
I'd be working base on that to try to bring support to the JC4880P433C board based on that.

[Lzw655]

I think you're referring to the esp_board_manager component, and you can indeed try to support JC4880P433C based on it.

[sohil4932]

@Lzw655 Amazing, thank you so much for the update. Do we have a tentative timeline for this release?

[Lzw655]

This plan was initially scheduled to be completed in October 😥, but due to some reasons, it hasn't been finished yet. Therefore, I can only say that I am working on it with all my efforts. It is currently expected to be completed by the end of December, and there may be further delays. Sorry for that!

[csvke]

Just release before Chinese new year when everyone goes home 😂

[Lzw655]

Sure, that should be fine.

[ronger-x]

We designed a hardware based on szpi-esp32s3, adding NFC and an SD card slot. It only relies on three pins: DC/SCK/MOSI (without CS/RST), driving the SPI screen. We are wondering if it is feasible to port it to our current project?

[Lzw655]

You can try using the esp_board_manager component to adapt your development board. Products of ESP-Brookesia will utilize it to ensure compatibility with various development boards.

[yihua-wang]

@Lzw655 Will there be an update this week?

[Lzw655]

Yes, some Agent-related components should be able to be released this week.

[Lzw655]

Sorry for the late!

The Agent class component has been released, and a service_console example is provided to test all service functions. Please note that, since the initialization of audio hardware depends on the esp_board_manager component, and there is an issue with the latest version of this component, which is currently fixing, the Audio and Agent related services cannot be run on the service_console example at this time.

[yihua-wang]

brookesia_system_core
brookesia_system_phone
Then, regarding these two parts, what specific improvements will be made? @Lzw655

[Lzw655]

I am integrating the service framework into the components of the system and app. There are no other improvements in Release v0.7 besides these.

[yihua-wang]

So, in 0.7, are brookesia_system_core and brookesia_system_phone still the same as they are now?

[Lzw655]

In terms of functionality (such as UI), yes, but the structure and interfaces will be refactored.

[yihua-wang]

Hi,

I would like to suggest optimizing the component dependency structure of this project. Currently, some modules seem to have heavy dependencies on specific ESP-IDF components.

The main points are:

Minimize Dependencies: Could we reduce the coupling between modules? It would be better if each module only depends on the minimum set of components required for its core functionality.

Conditional Inclusion: For example, if a user does not need audio features, the project should not force the inclusion of the esp-gmf (ESP Global Multimedia Framework) library.

Modular Configuration: This would make the project more lightweight and prevent version conflicts (like dependency solving failures) when integrating with other components.

Are there any plans to make these large functional blocks optional?

Thank you!

[Lzw655]

Hi @yihua-wang,

May I ask which project or component's issue you are specifically referring to? For the current V0.7 components, the main thing is that the Audio and Agent-related functions directly depend on the esp-gmf component. If the project does not require audio-related services, it just needs to not depend on the Audio and Agent components.

[yihua-wang]

maybe
espressif/gmf_core:

[Lzw655]

I mean, which specific ESP Project depends on components like gmf_core? I guess you're referring to products/speaker, right?

[yihua-wang]

yeah My project is based on the phone. But I don't need the audio.

[Lzw655]

I see. Currently, the brookesia_core component does have this issue. Your idea is consistent with our plan, and this is exactly the problem that the V0.7 version is addressing.

At present, we have integrated the functions related to Audio and Agent into independent components. Through the service framework, applications no longer need to explicitly depend on components related to esp-gmf. Please rest assured that the phone and subsequent system components, they will not directly depend on components related to esp-gmf.

[yihua-wang]

@Lzw655 When can all the plans before 1.30 be fully updated?

[Lzw655]

Sorry, I've been working on improving the stability of the Agent recently, and also ported XiaoZhi.

It seems that it will need to be postponed to before February 18th (Chinese New Year).

[cagupusezod320-alt]

Every time you dive, it's the first day of the Lunar New Year on February 18th. Are you planning to work overtime? Keep it up!

[Lzw655]

Sorry, I’ll do my best to finish all the remaining updates before the Lunar New Year.

[yihua-wang]

How to use apps on the phone? It's not just about the speaker. @Lzw655

[diablo31985]

Looking forward to your updates