Arctory vs Power Apps: Same Shopfloor App, Same Excel Files (2026 Test)
Same shopfloor app, same Excel files: Power Apps imported 0 of 30 machines and needed 7 formulas. Arctory imported all 30, needed none and ran in 13 minutes.
By Eden Chabanet, Co-Founder & CEO ·
Test · November 2026
Your process owners already have Power Apps with Microsoft 365. We compared building a shopfloor app with Power Apps vs with Arctory.
We wanted to see this for ourselves, so we used Power Apps and Arctory to create an app for ticketing and tracking downtime. We generated 3 tables with mock data:
- 30 machines in Excel
- 60 past faults in Excel
- 2,400 orders from SAP
Finally, we asked a person with no development skills to create an app with both tools.
After 25 minutes alone in Power Apps, our tester didn't get an app. In her own words, she would rather stick to Excel or send the task to IT than figure out Power Apps alone. In Arctory, the first version ran after 13 minutes, with all 30 machines successfully imported from the Excel file. We then worked through the remaining Power Apps steps ourselves. You can download the task cards and files to repeat the test.
Power Apps
Arctory
No app
after 25 min of trying alone
62 choices
e.g. layout, data source, environment
8 choices
e.g. app name, user role
0 of 2
Excel files imported
2 of 2
Excel files imported
7 formulas
typed by hand, like SubmitForm(Form5)
0 formulas
every change in plain words
3 tools
Power Apps, Power Automate, admin center
1 tool
one chat for everything
The test, step by step
Both tools got the same seven steps. Power Apps passed two, so I'll start there. Click a step to jump to it.
Both tools passed.
Power Apps
Power Apps found it too, once the orders sat in Dataverse, but we had to figure out the four formulas ourselves. One of them counted "Orders loaded: 0", and the fix was in a warning that appears only on hover. We also discovered that Dataverse needs a Premium licence, and on a plain Excel source Power Apps searches only the first 500 rows by default.
Arctory
Our tester dropped the SAP export into the chat, and in under 4 minutes the app showed "2,400 orders loaded" and found X-1800.
↑ Back to all steps
Another pass for both.
Power Apps
The column Power Apps had generated already took 850 characters.
Arctory
It took one sentence and about a minute, and we checked by pasting 500 characters into the field.
That was the last easy step: from here on, for every change in Power Apps we needed a formula or help from Claude.
↑ Back to all steps
Operators wear gloves, so we wanted to turn the small check mark that saves a fault into a big green "Report fault" button.
Power Apps
That meant inserting a button and setting three properties in the formula bar, one of them SubmitForm(Form5). You can only write that if you know the form's internal name, so this is where we used Claude.
Arctory
Our tester asked for the change in one sentence, and it was done in under a minute.
↑ Back to all steps
Power Apps
We had to manually create a Choice column in the table designer, then add it to the form. When we reopened the app, Power Apps locked it as read-only "because you already have editing control elsewhere", against its own maker. That happened three times during the test.
Arctory
It was one sentence and 2 minutes: a required Shift field with Early, Late and Night.
↑ Back to all steps
This is where our tester got stuck alone.
Power Apps
Power Apps asks you to decide between 8 ways to start creating an app. In the trial, the first attempt ended at "You don't have permission to create here". And since the tester was using Safari she couldn't build apps at all. But this she only found out when she was trying to save her edits. When we built the app from the description ourselves, Copilot made one standard screen per table, with sample faults it invented (our Excel data wasn't imported), a report time typed by hand and a text field for the photo.
Arctory
Both Excel files went into the chat with the description. After 13 minutes the first version ran with the plant's machines and fault history.
Over the whole test, Arctory asked us for 8 choices and Power Apps for 62.
↑ Back to all steps
This was the make-or-break moment, because if Excel is not uploaded, the app would not help on the shop floor.
Power Apps
The Excel Online route in Power Apps needs the data formatted as an Excel table, and our file was a plain export, as ERP exports usually are: "Error loading". Uploading the file ended in "Unable to create app". Importing into Copilot's tables brought in 0 of 30 machines, and the importer suggested putting downtime into a system field called versionnumber. None of the 60 past faults had arrived 5.5 minutes later.
Arctory
Both files went in whole: 30 machines and 60 faults. The downtime overview added up to 3,692 minutes, and every line matched the totals we had worked out from the Excel.
↑ Back to all steps
Power Apps
The Share dialog warned that this is a developer environment and that colleagues need permissions on the app's data. The app is designated Premium, so everyone who opens it needs a Premium licence: €17.30 per user per month, billed annually, excl. VAT (Microsoft pricing, 9 Nov 2026). For 150 operators, that's about €31,140 a year, and shared tablets don't reduce the count.
Arctory
Our tester deployed the app, picked a colleague, chose the role "Use" and saved: 4 minutes, no licence prompt. Arctory is licensed per plant with unlimited users, inside the sign-in and roles IT sets up once.
↑ Back to all steps
What Power Apps did better
We also asked both tools to email maintenance about high-priority faults.
- Power Apps is native to Microsoft 365, so the alert could use our own Outlook sign-in, and the email arrived, after we fixed Copilot's draft by hand.
- Arctory built the same alert in under a minute, but it goes live only once IT connects the company's sending mailbox.
Why this is an IT question: shadow IT
None of these steps is hard for a developer. The problem is who has to do them. When a process owner gets stuck, they would either:
- send a request to IT, which Power Apps was meant to avoid, or
- simply continue in Excel.
But even if the person succeeds in creating an app for their needs, it stays in their personal environment, out of sight unless IT goes looking. Power Platform has admin tools for this, but someone in IT has to run them across many places: every licensed Microsoft 365 user can build in the shared default environment, and makers can open trial or developer environments of their own (Microsoft Learn).
We built Arctory so the process owner can finish the app while IT keeps control:
- Every app lives on one platform, hosted in Germany and GDPR compliant, so IT sees all of them.
- Your data never trains AI models, and once an app is live, the AI has no access to it.
- Single sign-on is optional, roles are managed centrally, and 100+ connectors reach SAP, Microsoft Dynamics 365, Infor, abas and more.
Details are in our security overview.
Power Apps or Arctory?
- Power Apps fits when a Power Platform team builds and maintains the apps, and the app lives inside Teams, SharePoint and Outlook.
- Arctory fits when the people who know the process should build the apps themselves, your data starts in Excel and the ERP, and IT wants every app on one platform instead of shadow IT. It's licensed per plant, with unlimited users and apps.
0 → 12
apps at Venti Oelde in 6 months
"The future of digitalization in production is the ERP system together with Arctory."
Lukas StoppaTechnical Director, Ventilatorenfabrik Oelde
Read how Venti Oelde builds its own shopfloor apps →
Trade magazine IT&Production calls the Venti approach programming in natural language.
Run the test with your own Excel
Same cards, same files, any tool: task cards, machines.xlsx, fault-history.xlsx and orders-sap-export.csv. Or bring your own list, and we'll build your first app with you.
Frequently asked questions
Is there a Power Apps alternative for manufacturing?
Yes. Arctory is an AI app builder for manufacturing: process owners describe a shopfloor app in plain language, and Arctory builds it with the interface, workflow, database and ERP connection. In our test, Arctory took in the plant's 30 machines and 60 past faults from Excel and had a working app in 13 minutes. Power Apps imported none of them.
Couldn't you just use a SharePoint list instead?
We didn't test one. A SharePoint list can avoid the Premium licence (licensing guide), but whenever a search can't be passed to the list, Power Apps works on only the first 500 rows by default, and 10,000 at most (Microsoft Learn). The Excel Online route, which we did try, stopped at "Error loading. Try again."
Can you build Power Apps apps in Safari?
No. Power Apps Studio supports only Microsoft Edge and Google Chrome; Safari and Firefox can run finished apps but aren't supported for building them (Microsoft Learn).
Sources
Microsoft pages read on 9 Nov 2026: limits and configuration, delegation, sharing a canvas app, Power Apps pricing and the Power Platform licensing guide. Press: IT&Production 5/2026, pages 78–79. Test recordings: 9 and 10 Nov 2026.
Screenshots: Microsoft Power Apps and Arctory, from our test on 9 and 10 Nov 2026. Personal names and IDs are blurred and the browser bar is cut off; nothing else is changed.
Microsoft, Power Apps, Power Automate and Copilot are trademarks of the Microsoft group of companies. Arctory ran this test; Microsoft did not review it.
Author
Co-Founder & CEO, Arctory GmbH
Eden spent ten years putting robots and software into production, at KUKA and at Bosch Rexroth with manufacturers such as Volvo, L'Oréal and Aptar. At Arctory she leads business development and the work with new customers. Arctory on LinkedIn
Back to the blog