La Place
We'll take care of a new flavour
Three situations we encounter every week.
An app on a phone isn’t being used. Without a recurring task, there’s no reason to open it—and we determine that reason before anything is built.
Status inquiries, invoices, order history: if customers have to call for these things, every answer takes up your time. In a portal, they can check it themselves.
If a small adjustment requires a new release and a store review, further development comes to a standstill. With the right setup, most of the work happens outside the app.
An app makes sense if there’s a task that someone performs often enough to warrant having an icon for it on their home screen. If that task doesn’t exist, a web application or a browser-based portal is usually the better solution. We have that conversation first, because it saves you from building something that nobody will use.
Next, we choose the technology based on the requirements: native for iOS and Android if the device itself is necessary, React Native if a single codebase suffices, or Laravel, Symfony, and Next.js for a web application or portal. We move as much logic as possible outside the app, so that an update doesn’t require a store review. Where technology can take over the work, we let it: usage data shows which steps are causing issues, and AI helps our developers build and review faster. The responsibility for quality and security remains with us.
You’ll work with Paul, Head of Engineering. He compiles usage data, crashes, and speed metrics into a dashboard that you can access yourself, so you can see after every release whether things have improved.
Four layers. The choice: native, hybrid, or web app, along with the rationale and the implications for management and costs. The functional design: which tasks the app performs and which it deliberately does not, developed into a clickable prototype before development begins. Development: the app plus the integrations with your existing systems, because without your own data, an app is just an empty shell. And the rollout: publishing to the App Store and Google Play, including reviews and subsequent updates.
Many requests that come in as “app requests” are actually “portal requests.” If you want to create a customer portal where customers can view their orders, invoices, contracts, or service status on their own, it doesn’t have to be an app: a secure browser-based environment works on any device and requires no installation. The same applies to internal portals for dealers, technicians, or employees. We build these as web applications on top of your existing systems, with roles and permissions, and with an integration that displays the data already available. Any issue resolved there will no longer be directed to your customer service team.
Three services that keep an app running.
An app never stands alone. The design determines whether the task is successful, the integrations determine what data is visible, and support ensures it will still work after the next iOS update. We handle all three within the same team.
From intake to ongoing development in five steps.
We determine what problem the app solves and for whom, and whether an app is the right solution. Sometimes the answer is a portal, and we’ll let you know.
We define the functionality, screens, and interactions in a clickable prototype that we test with users before development begins.
We build the app or web application and integrate it with your CRM, inventory system, payment provider, or ERP. We keep as much logic as possible outside the app.
We test the app on various devices, check its speed and security, and handle the submission to the App Store and Google Play, including the review process.
After launch, we monitor usage, crashes, and performance and make adjustments as needed. For each release, you’ll see whether the changes achieved their intended results.
From an app complementing the website to a private environment for business customers.
Three frameworks for apps, web applications, and portals.
In one hour, we’ll go over the problem you want to solve and for whom. You’ll find out whether an app is the right solution or if a portal would be more beneficial for you. It takes just one hour and doesn’t commit you to anything.
That depends on whether you choose a native, hybrid, or web app, the number of integrations, and whether a secure environment with roles and permissions is included. An app that integrates with existing systems is a different process than a portal that aggregates data from four sources.
What you always get: an honest answer to whether an app is the right solution, a prototype that’s been tested before development begins, integrations with your own systems, and a dashboard tracking usage and crashes.
Want to know what’s needed in your specific case? Schedule a meeting, and we’ll define the scope together.
That depends on the type of app, the desired features, and integrations. We always create a customized proposal after an initial consultation.
Native apps are developed specifically for iOS or Android. Hybrid apps (such as those built with React Native) run on both platforms from a single codebase.
Yes, we build powerful and secure web apps that work well in any browser and on any device.
On average, between 10 and 20 weeks, depending on the scope and complexity.
Absolutely. We provide support and updates, and we’re happy to help build new features.