AppSheet vs. Power Apps

Suitable for database work. Access controller for personnel, products, sales, distribution, etc. Not suitable for applications that require visual and graphic demands. There are graphically interactive applications that have buttons or action gestures that are not common. It should be possible, to create the App. Remove information relevant to the specific company or business for which the App was generated. And then be able to share it with other similar businesses independently.

PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution

• Calculations - I have several apps that do some pretty complicated calculations, and decision making to build things like Shopping Lists for a Kanban assembly team, where the app will help a stocker determine whats low in a kanban assembly line stock box.
• Document generation and record keeping - I have an app that users digitally sign and receive PDF contracts, and the system automatically records all records from the transaction. Everything is held in files on YOUR OWN DRIVE (Google Drive) so when you're done with the project or AppSheet you DONT loose your data.
• Client/Customer Management - I follow the old school "Swimming with Sharks" model for client retention and customer engagement, and have built several small customer tracking tools for local businesses. This tool is limited ONLY by your imagine and desire to learn.

Incentivized

• Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
• We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
• The online learning resources and tutorials are helpful as well for those who are tech savvy.

Incentivized

• GPS on the maps are terrible. We dont use the map to collect data as the signal is erratic only in Appsheet. We have another app installed on the same phone to get X,Y data which is copied and pasted into the appsheet solution. We have tried everything but Appsheet map and coordinate accuracy and erratic behaviour is below par.
• Deployment management. While it is great that people see your changes right away, it sometimes leads to downtime if one makes a mistake. In the beginning it was hard to tell which changes would negatively effect the users and in some cases the data got jumbled due to table changes. Would be good if development, testing and deployment were better streamlined. No need for auto testing (like selenium etc.) just a place we can test before deploying. Now we have several "dev" versions with a cumbersome copy and paste system.

• PowerApps has a great coding option, but there are some pieces of the tool that the requirement to understand code is a barrier to fun if the user doesn't code.
• MUCH time can be spent looking for solutions on this young platform and the body of forum/help/lessons learned is not as robust as it will be in a few years.
• Like many early-stage Microsoft products, PowerApps is a relatively blank slate that will be improved by the feedback of their users and ongoing feature development. Right now it seems that the product lacks a critical mass of use-case driven templates (there are some, but I haven't yet found one that didn't require more work to customize it to my need that it would take to build my own tool).

Incentivized

We are still less than 10 users and probably may continue to be so. But, this being a franchisor set up, could be of use to other users like us.

It's just great. The usability is the best thing about Appsheet. You must choose which things will really be used later. You have to be careful of not generating something too big and then it feels like something that need to be learned. This is something that resolve problems, but you had to be able to think before doing. It will not solve problems itself. You need to find the problem, think a solution, and then use appsheet to make this solution a reality

Incentivized

PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.

Incentivized

AppSsheet has a support group and they show videos to help app builders. Though I have truck drivers' hours and can't join the webinars. Support groups with better assists me on a Saturday evening or a Sunday that I have time off. It's hard to watch videos driving down the highway.

The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.

I did everything on my own

Incentivized

We started to try Glide, but we had already started our learning curve with Appsheet, and as the cost is part of our plan, the choice was easy. Since there is no cost for each feature we want to develop, Appsheet can serve as a replacement for tools like Docs, Sheets, and Slides. It just turns into another piece of software the employees are using, so thinking of moving to another product is nonsense.

Incentivized

1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.

Incentivized

• A good impact in general at the beginning since the free version allows great development so the investment in the implementation is of knowledge and time.
• As a consultant I have expanded my services through this platform including new low code application building services.

• Automation of manual processes brings an ROI on labor costs.
• Intake of data provides clean database design.
• Connectivity to data-lake provides insights and trends into the data.
• Able to scale operations with efficiencies provided by the app.
• Can mature the process and workflows to do more.

Incentivized