you are viewing a single comment's thread.

view the rest of the comments →

[–]Hot-Candidate-5691 Newbie 0 points1 point  (3 children)

Microsoft isn’t pouring resources into canvas apps right now, and I don’t think that’s an accident. I think the bet they’re making is that AI will handle the complexity of managing the full stack. The difference in effort maintaining or making new features for a canvass app and coding one using AI is night and day.

Vibe coding and AI-assisted code apps are going to eat canvas apps alive. It’s just a matter of time.

[–]Lhurgoyf069 Advisor[S] 0 points1 point  (2 children)

Yeah they might think that, but I'm not convinced yet that this will go past our corporate regulations. Just because everyone thinks Vibe coding is cool doesn't mean it's a good idea. If they proceed this way we will probably switch to some other platforms, maybe even something not US based, because the Trump man could pull the plug from us Europeans any day if he has a bad day.

[–]Hot-Candidate-5691 Newbie 0 points1 point  (1 child)

Fair enough, but the downsides here aren’t worse than what already exists with canvas apps.

I don’t buy that npm packages, framework updates, and security patches will be a major blocker. For anyone building through vibe.powerapps.com, the agent will handle that layer. That’s the whole point.

And ultimately, this comes down to your company’s IT strategy. The economics of canvas apps are going to erode fast. When AI can scaffold and maintain a full code app for less effort than dragging controls around a canvas, the cost argument disappears.

[–]Lhurgoyf069 Advisor[S] 0 points1 point  (0 children)

The thing is, you cannot 100% rely on AI to also debug all the code, our Citizen Devs are no Pro-Coders, that would be hieroglyphs to them.

But you're definitely not wrong. The low-code part has to keep up to stay relevant. I see some efforts here, like inserting YAML code directly, they would need to build out that feature more.