Installable business app for SMEs
Ai Flowi AI staff is an installable web app for small-business teams working on a phone or laptop.
Use this guide to choose which tasks to check on a small screen and which to prepare on the web. Workflow editing belongs on the web; phones run and monitor workflows.
The offline shell does not establish offline record processing or background synchronisation.
By Ai Flowi
Updated 21 October 2026; facts checked 21 October 2026
Documented product features. Read the evidence policy.
What installing the web app means
The app supports installation through a web-app installation prompt. It includes an offline page and a cached app shell.
That shell is the surrounding app interface; it is not evidence that a leave request, stock change or approval can be completed without a connection.
This page describes the installable web version. A native store app has not been verified.
Ask to see the installation prompt on the device and browser your team actually uses. Confirm the approved app destination during the demo, then record the installation behaviour with your own device details. Avoid planning a rollout from a generic installation checklist alone.
Match each device to a concrete task
Use the table as an evaluation plan. The documented feature does not establish that every browser, tablet or screen reader has passed a device test.
| Task and device to assess | Documented capability | What to supply or check |
|---|---|---|
| Phone: employee self-service | View own payslips, leave, attendance, claims, documents, team and performance; apply for leave or submit a claim. | Use synthetic employee records and the intended employee role; check only that employee’s permitted information. |
| Phone: attendance | Clock in and out, with geofence checks and regularisation requests. | Ask to see a permitted clock-in and a regularisation review on the intended device. |
| Laptop: workflow preparation | Draw a flow, validate it, test-run it, publish it or pause it through web editing. | Bring a task outline and synthetic input; inspect the intended changes before publishing a configuration. |
| Phone: workflow follow-through | Run and monitor workflows. | Check the run view on the intended phone; prepare changes through web editing. |
| Tablet: task fit | Use a tablet demo to assess the web-app layout for your chosen task. | Check reading, navigation and form controls on the actual tablet; tablet compatibility is not established here. |
| Phone: reporting export | Reports generate a PDF from permitted data; native-phone download remains incomplete. | Check the export and receipt of the file separately before making phone-only reporting a requirement. |
Language and display choices
The product interface is available in English, Chinese, Japanese, Korean and Russian. A Malay interface is not included.
Website translations are separate from the languages inside the product.
Light, dark and black-and-white modes are available, with the system preference followed by default.
Selected states are announced for screen-reader use. These features do not establish an accessibility audit or certification.
Include a person who uses the intended display or assistive setup in your evaluation. Ask them to check whether the selected item is clear, headings are understandable and important controls can be reached. Record problems against the task rather than assuming a display mode resolves every access need.
Screens load on demand. No loading-time or connection-speed result is claimed here.
Illustration: a leave request and a workflow review
Illustration – example setup, not a customer result.
For an example setup, choose an employee role to review its own leave information and prepare a leave request. The self-service feature supports that request.
Separately, choose a workflow to inspect from a phone. Ask to see its run and monitoring controls, then move any flow editing to the web.
Before the demonstration, write down the expected record and the person responsible for reviewing it. During the check, distinguish opening a screen, submitting a request and seeing its accepted state. Record an unresolved step as unresolved. This is a proposed evaluation, with no successful installation or completed request implied.
Permissions and decisions still matter
Department access and sensitive-field grants determine which records a role can see. Salary and bank data require additional verification.
Use the security and access guide to plan the roles for your demo, and the approval guide to check the decision controls.
AI reversible writes wait for approval by default and an owner can set them to run automatically; irreversible writes and money actions always need approval; money actions need a second approver; approval never moves money.
What is not included yet
- Offline transaction processing, queued offline submissions and guaranteed background synchronisation are not established by the offline shell.
- Native store-app availability is not established.
- Native-phone report download remains incomplete.
- Interface language support does not prove generated-answer quality or external message delivery.
Bring a device checklist to the demo
- List the phones, tablets, browsers and assistive tools your team intends to use.
- Choose a small set of synthetic tasks and write the expected screen, record and review step for each.
- Check installation, reopening, navigation and the selected display and interface language separately.
- Ask what remains visible without a connection; confirm any submission result after reconnecting rather than assuming it was stored.
- Record each unmet requirement and its owner before deciding whether the setup fits.
For department scope, read HR and payroll and inventory. Review the company operations guide for the owner’s wider task view.
Publisher: Ai Flowi. Send a correction or enquiry with the statement and supporting information to check.