r/PowerApps • Regular • Oct 15 '25

Discussion The make.powerapps.com alternative

Hey everyone,
I’ve been working on this project for a while and would love some brutally honest feedback from fellow makers.

Motivation:
Monday to Friday, I spend about 7.5 hours a day in the Maker Portal, and I feel that support, maintenance, and extensibility haven’t really gotten any easier. The roadmap still mainly focuses on new development.

I think the Power Platform is incredibly powerful, but it deserves a smoother maker experience that helps with extending what’s already there, debugging, and keeping things running.

So, I started building an alternative interface. An Alternative AI-assisted Maker Portal called 'Dynamics CoLab'. Conversational D365 & Power Apps customization
Describe what you want in plain English, and it handles the customization.

It’s still early, starting with model-driven apps, but already functional enough to test.

Question time:

Do you see this fitting into your workflow? If yes, where could it make the biggest impact?

Which features or improvements would make the biggest difference for you as a maker?

I’d really appreciate any feedback!

Edit:

Thanks everyone for taking the time. It was a super helpful thread.

main takeaways: i need to earn trust (fair), supporting the entire platform solo is too complex, and there’s potential for rapid prototyping.

So i’m pivoting: CoLab isn’t “a maker portal alternative” anymore. it’s an 'Easy-Maker version'.
goal: help newcomers escape excel and build their first powerapp fast. I’ll ship simple templates users can extend to fit their needs using AI

Also prioritize “fewest clicks possible”. To do this i’m also trying an app-first model (Meaning i will remove the concept of a 'solution'): show customizations in the app context so it’s obvious what’s included and where changes live.

Would love your take on this!

0 Upvotes

14 comments sorted by

36

u/DonJuanDoja Community Friend Oct 15 '25

Just to be honest I don't want any 3rd party plug ins or apps or anything unless I know it will be maintained over time and is being built and maintained by a stable company that can be relied upon for years to come.

Too many times I've found a tool or plug in or something that ended up dying because it wasn't maintained.

With the cloud and powerplatform constantly changing, I believe this will be difficult for any single developer to maintain, especially over greater lengths of time.

Don't listen to me though, keep going I hope you make something really awesome and it leads to better things for you.

7

u/einstein-314 Newbie Oct 16 '25

I have enough doubts for Microsoft themselves breaking and not maintaining compatibility. Not saying it’s impossible, but the bar is pretty high for me.

It would require a lot of assurances and I mean like having the head of the Microsoft product as my in laws, with some sort of blackmail. And enough confidence and execution experience in the 3rd party product to the level of Chic-fil-a. Only with both of those levels of confidence would i take on a major 3rd party plugin.

1

u/FrostyMari0nberry Regular Oct 16 '25

Thanks, that’s a really good point. I’m curious though, do you think there’s a level where an independent project can earn that trust?

Like if it’s open source?

4

u/csonthejjas Regular Oct 16 '25

Make it good enough and MS will buy you out and/or hire you.

1

u/FrostyMari0nberry Regular Oct 16 '25

Could be cool. But for this to play out I will have for it to be truly useful first and have actual users. To get to that I will still need to solve the issue on how to gain user trust. Right?

Wonder how the guy that made the TabularEditor managed to gain user trust… I’ll have to go look into that

1

u/FrostyMari0nberry Regular Oct 19 '25

Thanks for taking the time to answar. It was a super helpful thread.

main takeaways: i need to earn trust (fair), supporting the entire platform solo is too complex, and there’s potential for rapid prototyping.

So i’m pivoting: CoLab isn’t “a maker portal alternative” anymore. it’s an 'Easy-Maker version'.
goal: help newcomers escape excel and build their first powerapp fast. I’ll ship simple templates users can extend to fit their needs using AI

Also prioritize “fewest clicks possible”. To do this i’m also trying an app-first model (Meaning i will remove the concept of a 'solution'): show customizations in the app context so it’s obvious what’s included and where changes live.

Would love your take on this!

4

u/mechapaul Advisor Oct 16 '25

I’d second this.

8

u/ItinerantFella Advisor Oct 15 '25

In the experiments I've done so far, it takes me longer to accurately describe what I want to.a transformer for it to be able to make the changes I wanted. Faster and easier to change the configuration manually.

1

u/FrostyMari0nberry Regular Oct 16 '25

Yeah I’ve noticed the same when testing it myself. It takes a while when you have to give the agent all the context first.
A way of working with this is that users can actually see the elements in a solution, just like in the Maker Portal, and then select objects and ask in that context.

For example, selecting four fields and a form and saying “make sure these fields are hidden when X”.
Then the agent finds the best solution based on your existing setup and notifies you when it’s done.

Would that way of working change your view on it?

3

u/Byttemos Newbie Oct 16 '25

Despite my many gripes with the maker portal, my two biggest ones by far is slow performance and lack of granular, and intuitive, control. A purely conversational interface would not solve any of those (maybe performance could theoretically be improved, but I maintain skepticism regardless).

If I would disregard my personal needs for the maker portal, I think a tool like this has most of its' use in the early development stages of a new app. When you start completely from scratch, i imagine this could get you off to the races much quicker, even as a rapid prototyping tool.

For maintenance, however, we tend to want something extremely specific changed in the app, and I don't see conversational AI handling that well at this point (but then again, neither does the maker portal, so I digress).

It is a cool idea though, and like I said, there's a definite potential for rapid prototyping for sure!

1

u/FrostyMari0nberry Regular Oct 16 '25

Thanks for taking the time to write this, really appreciate the feedback.

Yeah, performance is a tough one since it can’t be faster than the Microsoft endpoints. I’ve done a few things like async operations and caching solution metadata to make it feel a bit snappier though.

One of the things that always bugged me in the Maker Portal is figuring out what logic actually affects a specific field. Being able to just ask the agent and have it find and list all the related cloud flows(workflows and BR's) and give a short explanation of what they do has been really valuable in my own debugging as well as onboarding on new solutions

3

u/Byttemos Newbie Oct 17 '25

I really wish MS would focus more on performance optimization for that exact reason, because that is the bottleneck with any custom tool.

I started a new position in a small NGO 6 months ago, and trying to get a lay of the land in terms of automation, business logic and dataflows is still an ongoing nightmare. That's partly why we've pivoted to a code first approach, limiting the use of power apps to UX/UI as much as possible, and instead handle all logic and automation with Azure.

That being said, when a solution to a problem is to avoid it, it's less of a solution and more pf a coping mechanism in my opinion, so I appreciate people like you, who tries to create solutions to the problems instead

1

u/csonthejjas Regular Oct 16 '25

Also MS is pushing hard on Plans, which is basically the same thing as this.

1

u/tpb1109 Community Friend Oct 16 '25

Not really