Our software · PROWERB
PROWERB develops web applications for specific product, campaign and operational tasks. User journeys, data and integrations are planned together and tested against real workflows.
Identify the central user task and the intended result.
Organise information and actions clearly, including on small screens.
Agree data, access and updates for ongoing use.
The product brief defines which devices and operating systems the app should support. This determines test devices, publication and ongoing maintenance.
AppleiOS as a possible target platform
Android as a possible target platform
Operating system updates, store requirements and new devices can change a companion app. Before publication, we agree supported platforms, who authorises changes and how testing, maintenance and service are organised in daily operations.
Atlas & Nexus · PROWERB systems
Atlas gives clients access to products, stock, campaigns and orders. Nexus supports operational processing. We agree the views and handovers needed for your project.
MEP and MRM describe tasks in marketing and material management. These are the PROWERB products for shops, campaigns and operations.
The example starts after unboxing a connected lamp. The app helps with pairing, provides suitable everyday controls and guides the user to support when something fails. Each situation needs a clear next step.
Development also covers the transitions: what happens when the device cannot be found? Does a setting survive a restart? What information does support need so the user does not have to repeat the entire story?
Identify the device, explain prerequisites and help resolve a failed connection. The goal is the first successful use.
The most frequent task gets the shortest path. Settings, feedback and status must match the actual device.
Instructions, product identification and contact belong together. Test the support handover with the team that will handle it.
Five building blocks, each commissionable individually, together a digital product presence.
Product-companion apps are built in the IT & Digital Hub Düsseldorf, the same unit that builds our own technology: the ERP and warehouse system PROWERB CORE, the MEP platform with its 18 modules, the reporting. Whoever builds systems for ongoing operations every day builds apps differently — for maintainability, for years. After launch, the app stays in our care, with fixed responsibilities for updates, incidents and expansion.
A speaker manufacturer building its brand came to us without any digital infrastructure. PROWERB developed the presence from the ground up: brand, website, online shop — and a product-companion app for the manufacturer's speakers. Plus partnerships in the hospitality space for market access. The app here is not an add-on but part of the product: it accompanies the devices in their users' everyday lives.
Workshop with product management and sales: what must the app do, who uses it, what belongs in the first release?
User flow, screens, CI implementation — coordinated with brand and product development.
Implementation in iterations, tests on the real device, sign-off by the customer.
Store publication and handover into ongoing operations.
Updates, incident resolution, new features along the product roadmap — as an agreed ongoing service.
These decisions define scope, responsibilities and acceptance.
Prioritise a fully usable core task and its failure cases. Additional features are placed in later steps with effort and dependencies identified.
The protocol, test devices, firmware and technical contacts must be available. A polished interface still needs a verified hardware connection.
Define store accounts, approvals, updates and responsibilities before launch. Acceptance takes place on the agreed physical devices.
A promotion app belongs to a campaign: log in, collect points, scan QR codes — over once the campaign ends. A product-companion app belongs to the product and lives as long as it does. You'll find sweepstakes and promotion apps under Promotion & Sweepstakes Fulfillment.
Yes. Starting with the app alone is possible. We connect existing systems rather than replace them.
Under your brand. PROWERB develops and operates in the background — in the store, in the app and in communications, only your brand appears.
For products that need to be set up, controlled or registered — or whose use depends on content: connected devices, technology requiring explanation, products with service needs. Whether an app is worthwhile, we clarify in the briefing, before the first line of code.
Describe the product, the target group and the occasion. We'll respond with an assessment of what the app must do — and what it doesn't need to.
