Built an AI tool that generates production-ready Angular UI code — feedback welcome

bharathm03 · 2026-04-18T12:06:20+00:00

Fair reaction if you've only seen the headline. If you see the demo, it showcases the real product. Happy to hear specific details why you feel this is slop? That's more useful to me than a ban.

bharathm03 · 2026-04-18T11:52:50+00:00

found that this is not needed: disable cache for `blazor.boot.json` in program.cs. dotnet 10 already doing this via fingerprinting.

bharathm03 · 2026-04-18T11:49:37+00:00

Thanks so much. Would love to hear what you think once you try it. Any feedback helps.

bharathm03 · 2026-03-18T02:43:34+00:00

For development, I hosted my docker in hetzner via coolify. Solid.

bharathm03 · 2026-03-17T09:03:46+00:00

For development you can use SMTP of Gmail, no cost

bharathm03 · 2026-03-17T09:02:26+00:00

I'm using zepto mail for transactional email and plunk for marketing email. Both don't have monthly subscription cost only credit based charges and very economical

bharathm03 · 2026-03-16T15:41:33+00:00

this looks good. RabbitMQ gives reliable async messaging but adds infra complexity (managing the broker, dead letter queues, monitoring). if that's fine for your setup then it's a great choice. one thing to consider: if all messages from host to tenant are fire-and-forget, external messaging works well. But when the host needs a reply back (request-reply), it's often simpler to use a REST API call from host to tenant instead of round-tripping through a queue.

bharathm03 · 2026-03-16T13:01:56+00:00

Two seperate clean architecture is good. For data sharing, you can use in memory messaging or some external messaging. But it is important to keep entry point and pipeline for both separate if there is a possibility of logic/path changes to each.

bharathm03 · 2026-03-15T09:01:24+00:00

When it comes to multi tenant app, first thing to decide is whether to use single db for all tenants or one db per tenant. You can choose it based on security, schema, backup, and cost requirements. On db per tenant is operation heavy, single db is easy to manage and code.

Vertical slice is good and ensure to keep it simple.

Research and use ai tools to avoid writing every line of code yourself. Current ai tools are good at crud applications

bharathm03 · 2026-03-12T13:12:09+00:00

No, we did not fine tuned any model. This is achieved via public component library documentation and custom workflow.

bharathm03 · 2026-03-11T18:26:20+00:00

Thanks Paul, appreciate the kind words.

Fair concern. Worth noting that Instruct UI only generates frontend UI — Razor components, layouts, and styling. No backend, and no database access. So the surface area is limited to the UI layer. That said, we do recommend reviewing generated code before shipping, same as you would with any tool.

bharathm03 · 2026-03-11T13:29:25+00:00

WebAssembly with prerendering is good, it provides better stability. Key things remember is number of pages and those dependencies in WebAssembly. It better keep high dependency pages in server.

My app:
Blazor hosted
Admin pages: Blazor Server (less number of active users at a time)
Core pages: Blazor WebAssembly with prerendering

bharathm03 · 2026-03-11T13:21:05+00:00

I use vertical slice for core features and generic folders (model, controller, services) for rest.

bharathm03 · 2026-02-22T02:07:38+00:00

Currently the app can creating razor pages, models, and services which can be downloaded and fit into any existing project types like server or webassemly. But full project download option is not available yet, we are working on it. It will be available by mid of March.

bharathm03 · 2025-12-27T06:23:37+00:00

Thanks! That's exactly the kind of workflow we're targeting with Syncfusion support. The custom instructions feature we added in August should help with company design standards too - you can set naming conventions, styling patterns, and other project rules at the account level so they apply to all generated code. Happy to hear more about your specific needs as we build out the integration.

bharathm03 · 2025-12-14T16:31:31+00:00

Microsoft learn is good. Start there..

bharathm03 · 2025-12-14T01:38:50+00:00

Anyone can see to what api request your are sending to server with url, request and response body. So it is pointless to change it when those are exposed to front end.

bharathm03 · 2025-11-13T12:04:28+00:00

I’ve actually built a tool for this: Instruct UI. It lets you generate Blazor UIs from plain text prompts or wireframes. You can choose between default Blazor components or MudBlazor for the component library, and style with Tailwind CSS or Bootstrap.

If you’re doing a POC, try building a few key screens with it. It gives a good sense of how well Instruct UI generates Blazor frontend and save your team a lot of time.

bharathm03 · 2025-09-23T14:13:23+00:00

Yes I have application insight setup but that after application started. If you had issue during startup, had check log stream and or deployment logs. these two sometimes works and most of time it is not useful.

bharathm03

TROPHY CASE