 Sue has a question. She says, I work in a company that provides field services and we're facing challenges in efficiently managing field reports and customer service requests. I'm interested in developing a custom application using Power Apps that allow field workers to easily submit reports, access customer information and update service statuses in real time. Can anyone provide insights into how to start building such an app? Additionally, what are the key considerations for ensuring the app is user-friendly, especially for our staff who are not very tech savvy? Again, not a small question. One suggestion I would make is to kick it off. I've done this before as a project and it was basically just using Power Automate along with Microsoft Forms. And it's already integrated. When you go to automate and you set up the app, you can actually, there's an option to include a Microsoft Form within the app and be able to design that form just like you would any other form. So that would be the place where they could actually fill out that information, get updates on that information, but then it goes, you take the Power App and you'd have to go back. You'd have to have some kind of database back end or something that could correlate that data because you're gonna have a lot of people that are gonna be entering data. So you would have to integrate maybe a Azure SQL instance or even some kind of data lake or something to on-premises SQL. I'm not sure how you would set it up, but it can all be done through the Power Apps. Power Automate is part of it, but Power Apps is what really drives that. So. Isn't that dynamics? Isn't that the customer service? It is, but dynamics is a separate piece and dynamics actually costs a lot more money than Power Apps does. Yeah, I always wonder though, is it worth it to have to develop? How much it's gonna cost you to develop something brand new? Yeah, but dynamics is also a full CRM, right? So you're not talking about something that does a specific task. You're talking about something that can do like a thousand different things as a CRM and I don't know if they wanna go that far. Absolutely, but try and keep it simple. I would suggest using just Power Apps. Well, I guess mine would start out, let's document what the requirements are because do they even need Power Apps? Because I've built a very similar thing previously and I didn't even use Power Apps. Use Power Automate, use Microsoft forums, SharePoint lists, they had tablets. What is there? There's a scenario we're missing. They're ultimately saying I need to go to Power Apps. I don't know if they do. I think there's a whole lot more information and they need to start by building out the requirements, what's in those forms, then see with the tools that you do not have to do major development on, does it fit the bill and then progress from there? Because I feel like they're just jumping into the deep side of the pool and instead of wading into that. Again, this is one of those, we need more information type of questions because I mean, literally, I don't know, old school here, you could do all this in access. So if you wanted to, you could basically set up forms and access and do it that way. So there's a hundred different ways you could slice it. The difference between forms and Power Apps is whether or not you need interactivity. If you just need to push information into the system, then the form solution with Power Automate to put it all into the right places in SharePoint is fine. But if you need interactivity, if you need to be able to look up existing ones as well, then you're going to want to switch back to Power Apps on a Canvas app. And I noticed in, if you want to go an extra step further and you don't want to have to use the Power Apps app on your devices, there is a new feature, I want to say it's called WRAP, maybe, where it will save it to native iOS and Android apps that you can then put in the store and the end users can download onto their devices directly as their own app as well. So all good information, all good and reasonable possibilities are available from what all of the speakers have said. And it's all right. But regardless of what tool or platform you're going to decide on, you're going to need to have some type of data model that's more complicated than it really is that reflects the requirements that the users in the field are gonna have to capture. So I would suggest as a starting point, do something very simple that you don't have to invest any time into Power Apps yet or any of the other solutions yet. Maybe use a Microsoft list and just start to lay out what the right columns would look like just like you would in Excel to match that requirement, meet that requirement. And there's some built-in native capabilities inside of the list where you can update the form, you can move the columns around to have a flow of the business process. You can add dynamic rules, you could do things that can grow with you. But before you get into the tool to find the requirement, should drive with that data model looks like regardless of the solution you go to, you're going to have a place to store the data, you're going to need a place to store the data. So you need that data model. So start with the data model and let that be the driver behind whatever you decide. And there's time to maturity, like today list, tomorrow Power Apps. A year from now, hey, let's go dynamics. So there's growth and there's opportunity through. I haven't had any experience with it, but would there be anything that comes with teams for frontline workers that would be a solution for this? So, because that came to mind as Krishna you were describing what she was needing. I don't know what teams for frontline workers won't allow you to do, but if you can add a list as a tab or any other app that is built, then you would think you'd be able to use that as your delivery platform. But internal to frontline workers, like what the building blocks are, I think they're just going to come into Teams apps that we love and use every day. Yeah, that's actually what I was thinking of you. So if you use the dashboard with the connections that ties into Teams, we've actually done that for some of our clients where we've used that dashboard and put buttons that go to forms or information there just so that they can see it right there on their phone and it gives them exactly what they need. They just click on the button, do what they need to do. And like Norm was saying, make it super simple where they can do something easily and then just kind of grow from there. Again, we can keep talking, but are we adding value?