Software & Cloud Development

Mobile development

Mobile rarely stops at one app: customer and staff apps, the APIs behind them, company devices and security policies. We choose the right approach for each need and build a capability that fits your IT.

Who this service is for

A good fit if

  • You need several customer or staff apps built on one consistent foundation.
  • Field staff need ERP, CRM or work-order data, sometimes without coverage.
  • Apps must meet your security policies and run on company-managed devices.
  • An existing app is hard to maintain, poorly reviewed or behind OS updates.

What is included

  • Mobile assessment: users, use cases, devices, connectivity, security
  • Platform recommendation (native, cross-platform or PWA) with written trade-offs
  • Shared architecture: APIs, sign-in, push, analytics, crash reporting
  • App design and build for iOS, Android or both
  • Secure API integration with ERP, CRM, Microsoft 365 and more
  • MASVS-informed security testing; Intune device configuration guidance

What this service is

The strategy, design and engineering behind your mobile apps, customised to your brand and goals and connected to your IT. One specific app? See mobile app development.

ApproachBuilt with
Native iOSSwift and SwiftUI
Native AndroidKotlin and Jetpack Compose
Cross-platformFlutter, React Native or .NET MAUI, built once for both
Progressive web appInstalls from the browser, shares code with your web platform

We recommend an approach per app, not one framework for everything, and write down why.

Mobile for the workforce

Staff apps are often the most valuable: inspections, deliveries, maintenance, sales visits, stock counts, site reports. They work where coverage is poor and feed data straight into Prometheus ERP, ERPNext or your work-order system, on company-managed phones, tablets and rugged devices.

  • Photos
  • Signatures
  • Barcodes
  • Locations

With our managed IT services, app deployment matches how your devices are enrolled, secured and supported.

Secure, consistent and current

Same security rules

Phones get lost on networks you do not control: secure storage, your sign-in with MFA, minimum permissions.

Cheaper next apps

Shared sign-in, APIs and components cut the cost of later apps.

Less re-entry

Data captured on a phone goes straight into the right system.

Kept current

Planned around yearly OS releases and store rules; dependencies updated, crashes monitored.

Store disclosures reflect what each app actually collects; the Nigeria Data Protection Act 2023 (NDPA) shapes the design, with health data treated as sensitive personal data (not legal advice). Costs are planned release by release, estimated in naira (or US dollars where a licence or service is priced in dollars), so the portfolio grows instead of becoming one-off apps nobody maintains. Support after handover needs a separate agreement; managed-service clients can add app backends to 24/7 monitoring and support, with response targets set in the service agreement.

Delivery

How the work is delivered

  1. Assess

    Who needs mobile access, for what, on which devices and where, including poor coverage.

    Output: Assessment and platform recommendation.

  2. Architect

    Shared foundation: APIs, sign-in, notifications, offline data and security controls.

    Output: Architecture and roadmap.

  3. Design and build

    The first app in short iterations, with test builds on real devices.

    Output: iOS and Android test builds.

  4. Test and secure

    Functional, device, accessibility and security tests, on poor connections and older devices.

    Output: Test evidence, release candidate.

  5. Release and maintain

    Public stores or private distribution, then updates planned around yearly OS releases.

    Output: Released app, maintenance plan.

Scope at a glance

Not included unless agreed

  • Devices, developer program fees and device management licences
  • Whole-fleet configuration, unless through our managed IT services
  • Legal review of privacy policies and store disclosures

What we need from you

  • Developer accounts in your name; brand assets, content, approvals
  • Access to your identity provider and connected systems
  • Representative testers and devices, including older models

Before handover

  • Real devices and OS versions, not just simulators; VoiceOver and TalkBack checks
  • Sensitive data in secure storage; agreed MASVS controls; offline edit conflicts tested
  • Release process, signing keys, store accounts and pipelines documented, in your name

What affects the cost

  • Number of platforms and apps
  • Offline operation and data synchronisation
  • ERP, CRM and other integrations
  • Security, device management and device range supported

No package prices: estimates in naira from an agreed scope, taxes shown separately.

Questions buyers usually ask

Native, cross-platform or a progressive web app?

Native (Swift, Kotlin) gives fullest device access and platform feel; Flutter or React Native share most code, often for less. Occasional users needing no device features or offline work may be served by a responsive site or PWA at lower cost. We recommend per app.

How do staff apps get onto company devices?

Privately, through Apple Business Manager and managed Google Play, pushed by a device management tool such as Microsoft Intune. They never need to appear in the public stores.

Can apps work without a connection?

Yes, with planning: data is stored on the device, changes queue and sync when a connection returns, with clear conflict rules. Offline adds cost, so we scope exactly which tasks need it.

Who owns the app store accounts?

Your organisation should. We work under delegated access, so apps, signing keys and store listings stay with you if you change providers.

Planning mobile apps for customers or staff?

Tell us who needs mobile access, to what, and on which devices. We will arrange a conversation about the approach before anything is priced.