The project manager sits in the car outside the site, wants to book two hours, and finds only a table view in her ERP app that is unreadable on a phone. The ERP stays, but the interface does not fit the tasks. Replacing the system is too expensive for that.
How I work: with source · with approval · in your system.
Starting point
Existing systems are stable and needed. Their interfaces are often built for a desk, not a phone, and vendor extensions cost extra or do not exist. At the same time, data and logins should stay in the system, because otherwise a second truth appears. Anyone putting a separate interface beside the system has to answer that question first; otherwise, a year later, there are two user directories and two permission models.
What I do
I put a separate interface in front of the existing system. A middleware layer talks to the system through official interfaces; the interface talks to the middleware. The login stays with the system; the password is not stored in the browser, the session lives server-side in the middleware. Permissions are passed through, not reinvented. If the middleware fails, it refuses service rather than half-working.
I build for the tasks that actually occur: book time, select projects and work packages, look up knowledge, file a document. Add-on modules sit beside the system and can be enabled one at a time; each brings its own permissions and boundaries. The vendor’s core stays unchanged so updates remain possible.
Before I open writing paths, I build them read-only. Only when the data mapping is right do writes come in, one at a time.
Result
You get a working interface or module, the middleware layer, and a concept for permissions and operation. On request with explainer videos for the rollout, so the team adopts the new interface.
Example
Projectile Mobile, my internal development. A mobile interface with its own middleware layer in front of Projectile. It is my own work and not a product of the vendor. The login stays with the system, the password is not stored in the browser, the session sits in the middleware. The current state: the interface runs read-only against a test instance, write paths are locked. It is not a shipped product but proof that the middleware layer holds against the official interfaces.
Marketplace, enabled one by one. Around the same middleware layer sits the Projectile Mobile marketplace, my own interface, not a marketplace run by the vendor. In internal use are the knowledge assistant, the DMS module and DevLink. Automations are deliberately not enabled, because the approval and allowlist work from automation with approval has to come first. DevLink goes from a work package to a coding session and writes the AI cost to the ticket; only token counts and metadata leave the developer machine, no prompts and no transcripts.
DMS module, in internal use. Files with mandatory metadata, documents by upload or camera, every version with a SHA-256 checksum. Full-text search runs over OCR and filters by permission, retention periods are stored, access is logged. Projectile remains the master for basic data and is only read. The module accounts for GoBD requirements through immutability by checksum, logging and retention; whether the procedure satisfies them in a given deployment depends on your own procedure documentation.
Then an internal PWA for three branches, showing that a custom interface also works on a phone: Filmreif reference. It is in internal testing.
Limit
Modules use the vendor’s official interfaces. What the interface does not provide is not forced through workarounds. After a vendor update, the middleware layer must be tested; that belongs in operations, not in a footnote.
The second limit is maturity. Projectile Mobile currently runs read-only against a test instance and is not shipped. If you need a writing interface today, you get it as a project with its own acceptance, not as an off-the-shelf product.
How it runs
- Review tasks and interfaces: what does the system provide
- Design the middleware layer and permission concept
- Build the interface or module read-only, test with real roles
- Open write paths one at a time, set up connection and operation
- Support the rollout, on request with training videos
Common questions
Does the vendor have to agree?
Not for using official interfaces. For changes to the core or access to undocumented interfaces, coordination is needed, and then I ask first.
Where does the password live?
Not in the browser. The login runs through the middleware, the session is held server-side. That puts the secret in one place you can protect and log.
What happens on a system update?
The middleware layer is tested against it. If an interface changes, the layer is adapted, not the interface rebuilt.
Is this custom software or an extension?
Technically a separate application beside the system. To the user it looks like part of it, because login, data and permissions fit together.