Please share with the community what you think needs improvement with Microsoft PowerApps.
What are its weaknesses? What would you like to see changed in a future version?
By working on PowerApps, you will still be required to do some low level coding. However its a great tool for existing Microsoft Developers who can now churn out Apps and enable a seamless integration across the entire suite of Microsoft Cloud applications.
In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available.
The price could be lower.
Improvements to the capturing of geographic locations and integration with maps would raise my score of the product from seven point five to its maximum of ten.
I can't recall any missing features. Currently, the solution is doing a good job of meeting my needs. My target is to have an application that I can use for clients. I don't see Power Apps as being the long-term solution. They get expensive when you start to go to non-internal users. If there were to be external users, the solution would get expensive. The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you. For example, the software is almost guilty of being too powerful. The particular problem I had was that they recommended that I use Azure to do the login, to do the user authentication. Therefore, I set it up. However, it didn't work. I could not find the solution via documentation or online at all. Without knowing I could access technical support, I paid someone a couple of hundred dollars to try and figure it out for me and they couldn't figure it out. Eventually, I was just looking around and I came across one setting hidden away and it was set to false. I instinctively realized that it looked like it might be related and so I set it to true and all of a sudden everything worked. However, that whole issue could have been mitigated if the documentation just took that extra step and got into the nuances of the product. What I'd love to see them do is to sit down and clean up the interfaces. There are three different ways that you can program. I'm particular to using a Power Apps portal. There are three different ways I can edit my Power Apps portal website. Each of them kind of does a better job of doing some things than the other ones do. Therefore you're kind of in this in-between realm of having to choose between certain things if you decide to go with a specific approach. They really need to clean up the development environment so that t's straightforward and predictable across the different ways to program. It does things, such as, if you want to delete a particular field or table, you get this message that says you can't due to the fact that it has dependencies. It's really hard to find what those dependencies are. Items like that need to be clarified. The application is working great now, however, every once in a while it gets complicated and it's hard to navigate.
There is always room for improvement and with PowerApps, there is a long way to go. The flexibility and the user interface need improvement. The speed, as in how fast things can be done, needs to be improved. The workflow needs improvement and should be included in the platform.
I think installation and integration could be improved. It's tricky compared to other tools.
The availability of templates needs to be improved. I understand that the ecosystem around it is still developing, but we need more templates. I would like the entire ecosystem around it to improve. I would recommend adding AI components. Even though we can always connect to Azure for AI components, they should slowly start looking at adding some AI components to PowerApps so that out-of-the-box learning can be applied to process flows. Salesforce has the Einstein layer that works along with license platforms. PowerApps should also have something similar.
The solution is pretty difficult to understand. You need to educate yourself on the product in order to be able to effectively use it. The solution needs a bit more refinement in general. It's still a new product. There's a lot of improvements that can be made from a useability perspective. There needs to be better guides and documentation available for new users in order to help them properly understand the product and how to use it.
Microsoft should combine both the web and the mobile environment with all of the layers of development into one package. Currently, it's separated because Microsoft Power Apps does not cover all of these issues, so you have to connect to two different solutions. With Mendix for example, with one environment, the developers can create either a mobile app or a web app — it's an all-in-one environment. Microsoft Power Apps is not a service. For instance, if you want to connect to a database, it will be done via a database platform.
The pricing structure needs to be improved, the current information is confusing.
You can't add too many filters onto anything you build, otherwise, it will be very slow and it will affect your performance. For example, some companies want to use a lot of dashboards for Excel Spreadsheets or Sharepoint. If you put everything onto a mobile app, you won't get the kind of performance that you would if you just worked in Sharepoint. A mobile app has certain limitations.
Its user interface can be better. It is good, but it can be a bit clunky.
The user interface is pretty good, although it is a little bit clunky and can be improved.
The solution does work a bit differently on cell phones and tablets. We still have information on our SQL server and we need to migrate things over. The timing of doing that is going to be a little tight. We're not in production yet, so we're still working through some issues. However, by the time we are in production, I'm confident this solution will be ready.
When you capture a lot of data, the data becomes enormous. It's one of Microsoft's challenges that there is a threshold limit of 5000 items. It has to improve the threshold limit where it can handle data beyond 5000 items. I would like to see integration with on-premise business applications, complex business routes, and complex business workflows.
The connectors are the main components that reference the data sources, and these need to be improved. They have to both improve the ones that are already there and add new ones.
It would be good if this solution supports standard BPM notation. We are thinking of switching to a BPM solution next year because it is not a BPM solution.
I can't think of any features that are lacking. The pricing could always be less. I have heard from developers that there is documentation missing in the reporting. It would be useful if Power Apps were capable of providing more flexible reporting to allow the developer to really to manipulate the data, and get into more details - for example, why it's being changed and how it's been changed. If there was a way they could comment right in the reports, that would be very helpful. There should be more document management capabilities.
It is not enough user friendly. It also doesn't integrate very well with SQL Server.
For me, it's easier if I have visual references in order to learn the system. However, I'm also Spanish, and the tool is in English. That's one level of difficulty. Another level is that there aren't too many Spanish use cases and examples. It would help if there was more documentation in my native language to help me learn the system more effectively. In English, I don't think this is necessarily a problem. There seems to be a lot of English documentation. It would be helpful if there was more explanations built right into the solution's interface so that I can understand what action is supposed to get what result. In terms of usability, when I tried to make an amortization table, I couldn't find an exponential option. I don't know if it's ideal for financial tools that deal with credit or loans. I'm still looking into this. It's sometimes hard to import groups of options. At this point, I need to enter those manually and it slows the process down.
PowerApps is still a bit new compared to a slightly more mature product such as OutSystems. OutSystems has many features that are still not available in Power Apps. Simple things like navigation are better with Outsystem without much coding. The key is the licensing; the fees could be reduced, especially at the enterprise level. I would like to have more usability, with more fanciful navigation. More like what you would find in Outsystems BI. They offer more drag and drop navigation, and more advanced navigational options around the drag and drop lists and hierarchical navigation out of the box is literally a drag and a drop. It can be done in Power Apps, but you need to do a bit of coding to achieve the same thing. It's lacking in features.
Microsoft PowerApps is not intended for customizing what's generated in a major way. You have these little windows where you can enter your script and such, but there is no script debugging, nothing like that. You build and you auto-generate the code. From there, if you want to customize it too much, then it's going to get difficult — OutSystems was more intended for that; you can do a lot more customization after you build your solution.
The solution is limited in a very specific way. One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records. I connect to an Oracle server that has well over 150,000 records that business users want to see or could use at any given time. The only thing that I could surface in the app is a portion of up to 2000 records at one data call. Due to this limitation, I have to build in options for the user to refine the search, to go back out to the server, and then pull back records that match that search as opposed to offering all 150,000+ records. You need to filter quite extensively. Microsoft refers to is as a "delegation issue".
1. The licensing lakes a plan for a mass number of external users on the app. 2. The Data layer based on Azure data layer which complicates the environment, the min. required knowledge (citizen developers will not be independent under with PowerApps) and the vendor lock-in limitation. 3. The training is not integrated in the tool and the available training is not a full course which might be available in the online universities but not free and accessible like in other tools.
If they would reduce the price, that would be an improvement, and they should also improve their customer service support, because the last time I contacted them it took one week to resolve the issue. That's not right. I would like to see improvement in terms of implementation. Sometimes the application is a little slow. If I want to load the data from Power Apps, it generally takes time to take the data from experiential Power Apps, but in this case it takes longer compared to other technologies. I've written to them about this.
Integration with databases and other tools needs to be improved.
If you are accustomed to Microsoft technology, then it's quite easy to learn, but if you are new around the whole online platform of Microsoft, then it takes time. Even if you are familiar with Microsoft products then there is still a learning curve on the use. Previously with Microsoft, they were offering hands-on exercises or labs. I think that should be put back in place. Also, a few years ago Microsoft had an MVA program. It was called Microsoft Virtual Academy, where you could learn a lot about technology, but now it's deprecated and that's why it takes time to learn the new platform. I have always felt that you need an IT background to use this solution. I would like to see more regarding the help element of the program itself. More courses around the usage and of the technology features, more training, and guides.
The solution is evolving very fast and every month new features are introduced. Sometimes it's difficult to catch up with all the evolution that's happening. I had to focus on Power BI for a while and left PowerApps at the side for a couple of months and when I came back, it had changed its interface and moved components around. Some connectors are not very easy to use and sometimes they lack proper documentation. There should be better connectivity with other applications. I tried connecting with IBM and it brings errors at each refresh. The PostgreSQL connector is useless as it doesn't work. There's a lot of research needed and you often need to download extra drivers or equivalent components that end up not working well.
The product could be improved by making it a production application and enabling the export of apps. If you want to set up a site for home rentals, for example, just a basic outline as a starting point, this can be done. The issue is that it cannot be exported. It can be applied in-house, for demonstration purposes for your employees, for example, but you can't really make use of it otherwise. It's a problem. On the whole, it's a very workable solution because it's an automated way of making applications. You have a template, you have the application know-how, etc. If it could be exported into different languages and could enable different ways of outputting the information, that would be great. For now, it's limited and that's a bit of an issue. Enabling all the applications on internet-based devices to transfer data in and out would make it an excellent product.
The editor in the Web browser could be improved because it can be difficult to implement the commands in the buttons. In the next release, I would like to see Microsoft PowerApps be more integrated with Microsoft Teams or SharePoint and with different applications. When I configure PowerApps in Sharepoint it appears that it is not integrated with the page. When it is configured it looks like it is a different application.
Which would you prefer and why?