Thanks, i'll close this topic..
Thanks for the detailed explanation. I can understand the reasoning from ABP’s perspective, especially the goal of keeping the Admin Console separately upgradeable.
However, from a developer’s perspective—particularly for a junior developer starting a new project—the generated solution now seems to contain three separate UI surfaces:
Although I understand that we can generate code against the backend, I would expect a newly generated project to feel clean, consistent, and ready to use. At the moment, it is not immediately clear which application should be used for what or where development should begin.
Having the login and registration flow hosted separately is understandable. The Admin Console as a third distinct UI, however, makes the overall solution feel somewhat fragmented.
Is there a roadmap for bringing these experiences closer together or otherwise simplifying it?
Thanks for the clarification. If I understand correctly, the takeaway is that if you want to significantly customize the look and feel, you'll end up rebuilding quite a few of the built-in pages yourself.
That also applies to the Account/Profile pages, since they are part of the Admin Console. In practice, this means you would need to recreate those pages in each application as well if you want a consistent branded experience.
Is that a correct understanding? And is the ABP team considering improvements in this area, so that applications can achieve a custom look and feel without having to reimplement so much of the existing functionality?
AS in ....
Are there any plans to make the React Account module more similar to the classic UI approach? In the classic UI, the Account module UI (login, registration, password reset, etc.) can be downloaded as part of the ABP modules and customized within the application. It would be great if React offered a similar option, allowing developers to use and customize those pages without having to recreate them from scratch while still benefiting from the built-in ABP Account functionality.
Could you please verify the AI's answer? I'd also like to understand the roadmap. Specifically, is this something that's currently on the roadmap, or not?
How can we customize the styling of the admin console? It looks like it's provided as a NuGet package, so while we're able to style the frontend, the admin console always keeps its default appearance. Is there a recommended way to apply our own styling to it?
AI did not answer the question.
I have a question regarding low-code:
Can I already use this feature, or is it still in preview? If so, when will I be able to use it?
https://abp.io/docs/latest/low-code?LanguageCode=en
An answer would be appreciated.
AI agent answer is not relevant for us :)
I’m currently exploring the new AI-related features in ABP based on the following documentation pages:
https://abp.io/docs/10.0/framework/infrastructure/artificial-intelligence
https://abp.io/docs/10.0/modules/ai-management
I understand that these AI modules are currently in preview, and that’s perfectly fine for our use case.
I have a few concrete questions:
Is there anything specific we need to do or enable in order to start using and testing these AI modules in a real (but controlled) project?
Are there any important current limitations or “known gaps” we should be aware of when adopting the preview (e.g. missing scenarios, not-yet-implemented providers, configuration restrictions)?
What is the current roadmap for these AI modules?
Are there specific milestones or upcoming features you can already share (for example around agent support, orchestration, management UI, etc.)?
Do you expect significant breaking changes in the APIs/configuration as the modules evolve, or do you aim to keep the current abstractions relatively stable?
We have a concrete customer scenario:
The customer wants us to build AI agents using ABP-based application.
At the same time, the customer is building their own API endpoint so they can host and manage AI agents themselves.
Our application should act as a client to that external AI/agent API.
In this context, we would like to know:
Can we configure a custom chat client that calls this external API endpoint using the ConfigureChatClient configuration?
If yes:
What is the recommended way to plug such a custom chat client into the AI infrastructure / AI Management module so that it behaves similarly to the built-in providers?
Do you have a minimal example (or guidance) for implementing a custom chat client that forwards requests to an arbitrary HTTP endpoint?
Our goal is to leverage the ABP AI abstractions (for consistency and future maintainability), while letting the actual AI/agent logic run in the customer’s own API.
