PowerApps vs Plumsail Forms (Public Forms)
Introduction to PowerApps
PowerApps, as you probably already now, is a platform developed by Microsoft that allows building mobile apps with no need to write your own code (though knowledge of PowerApps syntax can be very helpful at times).
The process is fairly simple and intuitive, though some of the more advanced cases can be hard to figure out. Still, the platform is really powerful, and we’ve discovered these strengths to be at the core of platform’s success:
1) Variability and great integration – PowerApps allows you to create all kinds of apps, including Help Desks, Service Desks, Expenses Tracker, Case Management, and much more. What’s really important here – all of these will integrate well with your existing Microsoft’s environment, such as Flow, Teams, SharePoint, OneNote and others.
2) Easy to use, but offer complex functionality – while the product is relatively easy to grasp for beginners, but offer a robust toolbox to tackle the more specific uses cases. While it’s not necessary to write any actual code, chances are that you will need to use PowerApps syntax to attain the results you are looking for.
3) Mobile integration – let’s face, this is definitely the main appeal of the platform. While it’s possible to use PowerApps on PCs, they offer much better experience on phones and tablets, allowing many users to move away from the PCs and use their phones or tablets when working with PowerApps.
Introduction to Plumsail Forms
So, why are we talking about PowerApps? Because, our product – Forms, allows you to achieve the same goals as PowerApps, and in many cases allows even to work around the limitations of the platform.
It’s hard to pinpoint all the differences between the two, and have a fixed list of what advantages you can get with each one, as both PowerApps and our Forms are in active development, so we can expect new features to come to both. But we’ve tried to collect the information on how it is today, and what benefits you would get by using our product over PowerApps.
Truly public forms
While PowerApps allows creation powerful of apps, there is currently no easy way to share these apps with people outside of Office365 ecosystem. That means that while sharing with the users inside your organization might not be hard to implement (provided they all have an Office365 account), it makes sharing PowerApps much harder with users outside of the organization, for example, partners or customers.
Contrast this with Public Web Forms you can build with Plumsail Forms. Not only can you easily add these forms to your Office365 environment, such as a tab in MS Teams or a SharePoint page, but you can also publish these forms ANYWHERE in the web, for instance, on your own website.
All the data is collected by Microsoft Flow (alternatively, you can use Zapier), and then integrated into your own environment as you see fit. All you have to do is: design a form, configure a Flow, publish just a few lines of HTML widget to any webpage – and users would be able to submit data, no need to login at all! This data can then be used in SharePoint, stored in SQL, sent in an email, or otherwise processed by Flow, as you see fit.
An example form
Responsive very complex forms out of box
Designing forms with PowerApps web editor is not hard, true. And you can set up whether you create a phone or a tablet form, and adjust it accordingly.
But if you worked with PowerApps before, you know it can still be a struggle to achieve the precise effect you are going for. Implementing containers, such as Tabs, Accordions, Wizard would take a lot of time, and you would probably need to separate one form into multiple parts, and tie them together with custom logic.
Nothing like this is necessary with Plumsail Forms. First of all, forms are responsive by default – they’re based on Bootstrap Grid, and will scale depending on the size of the screen. For the more complex forms, you can configure different layouts for PC, Tablet or Phone – all within one form, simply changing how the form will be presented on different devices.
Secondly, you can create really complex forms with very little code, if any. Split form into parts with Tabs, Accordion, or even Wizard container, and drag and drop the fields inside – it all works straight away.
Custom controls and rich JS API
For example, you can include a DataTable, control which allows users to add rows to it. Each row has a set of columns which you set up in the designer. You can make certain columns mandatory, while others optional. You can also add other limitations to user input, or calculate some data, for example, Tax and Total values based on input in DataTable.
Alternatively, you can use Wizard Conainer, and separate your form into steps, where users must complete each step before moving on to the next. With the ability to write custom validators for each field, you can come up with unique interaction for each use case planned.
Pricing and Licensing
While PowerApps are licensed primarily per user, Public Forms offer a subscription license, with several plans depending on the amount of submissions per month.
So, if your Forms need to be used by a large number of users, it would definitely be more price efficient to use Plumsail Forms, as you would only pay for submissions, not for users. And even if the number of users is limited, you might find that our prices would most likely give you an edge over PowerApps, so it heavily depends on which products functionality suits you best.
Public Forms are published on a webpage, which could be either public or private, and would work well with both mobile and PC screens, so it’s not suited for app development, but if you are looking for mobile-friendly forms to connect to MS Flow – give Public Forms a try: