I have seen a lot of new features coming into Microsoft Power Apps over the last year, and the overall ecosystem is coming together much better now. It was more fragmented earlier, but it is getting together much better. I am focusing largely on the AI piece, including things like content extraction, image recognition, prompting, and automatic approval decisions. I am looking into more of that, so largely content extraction and AI-based workflows. I do use canvas apps. Given that Microsoft Power Apps is low-code, it makes things much faster and makes me think more from a functional perspective rather than consuming my time on implementation aspects or technical aspects. The low-code, drag-and-drop simplicity and the rich connectors which are available have really helped in the canvas app. Added to that, the AI feature now coming into the canvas app is also very helpful. A lot of time with Microsoft Power Apps, people just want plain vanilla data management with relationships across tables behind the scene and simple CRUD operations which are available in terms of create, read, update, and delete. If someone is not looking for anything fancy and wants something really quick, I usually start off with a model-driven app because it is pretty straightforward. There is a little bit of JavaScript and other few things which have now come up where you can actually customize a few things. In general, if the relationships are well-established in the data model behind the scene and you want something as plain as CRUD operations, model apps are very good. Another thing about model apps is that model-driven app provides uniform consistency. I was in the content management role in my company, and we always tried to come up with a uniform user interface that the entire organization can use. You have the list of entities listed on the left, and when you go into an entity, you have all the related entities that come down the drop-down box and you have standard main grid and record grid. It is a very standardized UI.
