An app project starts with an introduction: half an hour to an hour in which we go through the problem you want to tackle, the systems you have in place, and the expectations of management, IT and users on the shop floor. That conversation is free and non-binding. Often the outcome is: this can also be done with a progressive web app, or: an existing SaaS product is cheaper here, or: this is exactly the use case where a custom app adds value for your horticulture or logistics operation.
If there is a suitable use case, we plan a discovery. This is a short phase in which we work out the solution at architecture and interaction level: native or cross-platform, which integrations (FloraHolland data, ERP, TMS, climate computer, customs systems), which data flows, which compliance requirements, and what the release pipeline looks like. We deliver a concrete plan with scope, planning and budget, something you can use to make a decision internally rather than a vague direction.
Then comes the build, in sprints. At the end of every sprint, something working runs on real devices, limited at first and more complete each time. This helps you discover early what in the design doesn't work for the grower, the exporter or the driver, adjust priorities and bring stakeholders along. We work in your own repository, with code review, automated tests and a release process for both stores.
After go-live comes maintenance and optimisation. Apps need maintenance: new iOS and Android versions, changing APIs, performance tuning, store feedback. We offer ongoing support or hand it over cleanly to your own team, whichever suits you. For some clients in the horticulture and cargo sectors we have remained the permanent mobile partner; for others we deliver and provide support on request.