H5 Apps
An AI app builder for Infor M3 H5.
Describe the screen your team keeps asking for. LoupeCode builds it as a standard M3 H5 app, from the transactions and fields in your own environment. You preview it on your live M3, change it by saying what is wrong, and publish it when it does what you meant.
What comes out the other end
An H5 app, of the same kind a developer would have written. It is an Angular application built on Infor's H5 SDK, so it installs in H5 the ordinary way and behaves like everything else your users open there.
-
A standard H5 app, no extra licensing. Install it in any environment you have, move it from test to production, and run it without buying anything more. Ten users or a thousand, the price does not move.
-
Role-based access built in. Every app checks M3 roles before it opens. Pick who gets in using the roles that already exist in your environment, and there is no second user list to keep in step.
-
Every language your users speak. Add a language with a click and the whole app is translated. Each user sees it in the language they have configured in M3, automatically, including the ones you added after release.
-
Built from your environment. LoupeCode reads live metadata from your M3. Your fields, your custom fields, your transactions. Apps fit the system you actually run, not a demo.
-
Your look, if you want one. Set the colours and the type once and every app you build wears them, so what you hand to the business does not look like a tool's default template.
-
Source you can keep. Readable code, a full version history of every build, and a sync to your own git repository whenever you want it.
Start with one screen, not a project
An app in LoupeCode is a set of screens, and you add them one at a time. Start with the list the planner needs. Next week, add the detail screen it should open. The month after, add the entry form that replaces the spreadsheet. Each addition is another sentence, and the app keeps its shape.
Nothing has to be specified up front, because nothing has to be right first time. You are not paying for a change request, you are describing the change. Refining what you have already built is never metered.
Lists and filters
Sortable, filterable lists over real transactions, with the filter criteria as proper M3 lookups.
Detail and entry
Master and detail screens, forms that write back through transactions, and the validation that goes with them.
Whatever the job needs
Dashboards for planners, pickers for the warehouse, approvals for a manager. Describe the job, not the widgets.
Not a whole app?
If the change belongs on a standard M3 screen, build an H5 script instead.
Weighing it up?
How this differs from a low code platform, a generic AI builder, or a project.
Run it in your environment.
Bring an environment. We'll show you what one sentence can build. Already on Loupe? Just ask and we'll switch it on.