App development · Aprex

Apps that work where the work happens.

Apps for customers and staff, connected to APIs with offline support when needed.

Customer tasks, field work and controlled sync.

Illustration · sample data
Field task FT-208Mari · checklist 3/4 · saved locally
Prepare synchronisation
Local queue is visible01
Local and server values are compared02
User chooses before result is shown03
Field appLocal queueTask API
Chosen value shown in previewDemonstration · no camera, photo or sync is performed

FT-208 shows the queue and conflict before sync.

01 / Use cases

Apps for different users and situations

Give customers a mobile overview

Let customers follow cases and provide information.

See how

A customer app can show status from an agreed API and let people add information to a request without calling the team.

See an example

Support employees in the field

Bring tasks, checklists and notes into a work app.

See how

Staff open assigned jobs and record work on site, with clear status for the wider team.

See an example

Continue when the network drops

Save work locally and show what is waiting to sync.

See how

When coverage returns, local and newer server values are compared. The user chooses how to handle a conflict.

See an example
02 / See how it works

From offline entry to controlled sync

Follow example task FT-208 through a field flow with a visible queue and conflict check.

Sample data · no real actions

Example data

Example task

Task
FT-208 · service check
Field worker
Mari
Local status
Waiting in queue
Server status
Newer version found
Current step · 01 / 05

Open the assigned task

The app shows the assigned site, checklist items and current task status.

Task
FT-208
Checklist
3 of 4 items
See data, controls and log

Example data

Task
FT-208 · service check
Field worker
Mari
Local status
Waiting in queue
Server status
Newer version found

Controls

Local queue
1 change
Status
Waiting for connection

Your steps

No steps performed yet.

03 / Delivery

From first version to reliable operations.

  1. 01

    The right platform choice

    Assess app, PWA or website against actual use.

  2. 02

    A testable core flow

    Define forms, local storage and failure cases.

  3. 03

    Bounded integrations

    Agree sync, conflicts and access before build.

  4. 04

    Ready for operations

    Agree device testing, documentation and maintenance.

How we work

Products and services we operate

Do we need an app, or is a website enough?

It depends on platform requirements, how deeply the solution needs to use the device, and how the workflow runs. Aprex assesses together with you whether an app, a PWA, or a website fits best, and says so when a website holds.

What does app development cost?

Scope drives the work: number of platforms, flows, integrations, and requirements for offline, payments, and operations. An internal app against one API is different from a customer-facing app with booking, payments, and two platforms. Aprex gives no fixed price without seeing the need; send a description of users, devices, and systems for a concrete assessment.

More questions
Does Aprex build for both iOS and Android?

Yes. Aprex builds apps for both platforms and can connect them to data, booking, payments, and existing systems.

Can the app connect to our existing CRM or operations system?

Yes, when the systems have APIs, exports, or other safe integration points. Integrations are clarified early in the project, before the app flow is locked.

How does an app project start?

Start with one clear user group and one core flow. The first version should be tested on real devices before it is extended. Read about the method Aprex uses from mapping to operations.

Do you handle the App Store and Google Play?

Yes. Aprex prepares store listings, screenshots, privacy texts, and test flows, follows submission to approval, and handles updates afterwards.

What happens with new iOS and Android versions?

New OS versions can require app adjustments. Agreed operations and maintenance cover testing against new versions and necessary updates.

How is privacy handled in the app?

Data minimization, clear consent where required, secure storage, and deletion on need. Location and camera are used only where the flow requires it, and users are informed. Read more on the security page.

In depth: scope and delivery
When does an app fit best?

Choosing between an app, a PWA, and a website comes down to which platforms you need to cover, how deeply the solution needs to use the device (camera, push, offline storage), and how the work actually happens. Aprex assesses this together with you before choosing a solution. An app fits best when users are daily and mobile, when camera, location, push, or offline storage is central to the flow, or when distribution through the App Store and Google Play brings trust and reach. A PWA can hold where needs are simpler and the install threshold should be low. A website wins when content rarely changes per user and findability in search matters most. The wrong choice here is expensive, so Aprex settles the platform question before anything is designed.

Connected to your systems

Mobile apps for field teams, employees, or customers connect to data, booking, payments, and existing systems, so the app becomes part of operations instead of another standalone tool. That means APIs, data models, and access are planned together with the app itself: which data the app reads and writes, how conflicts are resolved when the same record changes in two places, and what happens offline. Login follows business requirements, with secure session handling and roles that mirror the responsibility the user already has. Payments and booking go through established providers where possible, so sensitive card and personal data is never stored in the app itself.

From prototype to the App Store and Google Play

Aprex keeps the same quality from the first prototype through publishing on the App Store and Google Play, and follows up with operations and further development after launch. The prototype is tested on real devices with real users, because simulators hide network drops, battery use, and how the app behaves with cold fingers in the field. Before submission, store listings, screenshots, privacy statements, age ratings, and test accounts for Apple and Google reviewers are prepared. After launch, Aprex follows up with fixes, adaptation to new OS versions, and development based on actual use, not guesses.

Three concrete cases as illustration

Illustration 1: Cleaners check in with geofence at buildings, tick off room checklists, photograph deviations, and sign digitally. The office sees per-building status in real time and exports documentation to the customer. Illustration 2: Customers book appointments, pay, and get push notifications on changes, while the company calendar and CRM update automatically without manual double entry. Illustration 3: Service technicians work offline in basements and plant rooms, register measurements and spare parts, and sync when coverage returns, with conflict handling that never silently loses data. These examples are illustrations, not descriptions of customer setups.

How we work, step by step

Step 1, platform choice: Aprex settles together with you whether app, PWA, or website fits, based on device use, offline needs, distribution, and maintenance budget. Step 2, prototype: One core flow is built and tested on real devices with real users. Step 3, first version: A complete flow with login, offline support, integrations, error handling, and accessibility. Step 4, store readiness: Store listings, privacy texts, and reviewer test flows are prepared, and submission is followed to approval. Step 5, operations: Monitoring of crashes and performance, updates for new OS versions, and development against measured use. Each step has clear deliverables before the next starts.

Typical systems and integration points

Apps rarely create value alone. Typical categories they connect to are CRM and case tools for customer and order data, booking and calendar systems for appointments, payment providers for purchases and subscriptions, map services for location and routes, push services for notifications, and internal APIs and databases for operations figures. Aprex builds against documented interfaces with versioning, so the app does not break when a backend system updates. Offline storage is designed deliberately: users should always see what is stored locally and what is confirmed received.

When an app is the wrong choice

An app fits poorly when users are rare and new every time, when content is static and findability in search matters most, or when the budget cannot carry maintenance on two platforms over time. It also fits poorly when the core need is covered by a good mobile-friendly website or PWA at a fraction of the cost. Aprex will say so when the analysis points there, and suggest a website or PWA instead. An app nobody installs or maintains is worse than no app.

Proof from our own products

Aprex operates apps, not just for customers. TapInn is operated by Aprex and used for mobile field work: geofenced check-ins, checklists, images, HSE, and deviations are registered where the job happens, even on poor coverage, and flow on to follow-up and documentation. The lessons from there - offline sync, simple registration with gloves on, clear notifications - are reused directly in customer projects. Hej CRM is Aprex AS's current CRM product. It replaces the earlier Farled concept. The product was previously named Dealo; see hejcrm.com/en for current product information. 24AI and 24Markets are lab products operated by Aprex showing that Aprex also masters web surfaces with continuously updated content where no app is needed.

Built for actual use

The app holds up against poor networks, bad input, and actual use in the field or with customers. Aprex apps are therefore tested on real devices with real users before launch, and operations with monitoring and updates are part of the delivery, not an add-on discovered afterwards.

Delivery at a glance
Provider
APREX AS
Primary email
post@aprex.no
Platform
iOS and Android
Builds
Field, employee, and customer apps connected to existing systems
Fits when
Platform requirements, device integration, or workflow point toward a dedicated app over a website or PWA
Typical start
A prototype with one core flow tested on real devices
More use cases and resources

Field apps

Check-ins, checklists, images, and deviations for employees working in the field. TapInn is an example of this operated by Aprex.

Read more

Customer apps

Booking, payments, and status connected to your own systems, with push notifications on changes.

Employee apps

Internal tools, notifications, and approvals for teams in the field or the office. See how field teams can work mobile.

Read more

Offline and secure access

Holds up on poor networks, handles secure login, and stays traceable. Read how Aprex works with security.

Read more

Push and notifications

Notifies employees or customers about status, deviations, or deadlines directly in the app.

Websites where no app is needed

Sometimes a website is the right choice. Aprex builds both and recommends honestly.

Read more

Ongoing operation

Maintenance, updates, and further development after launch, including new OS versions.

AI agency for small business (resource)

How a small business picks the right technology and AI partner.

Read more

What would you like to get done?

Tell us where work gets held up. We will explore the options together.