Mobile app developmentiOS and Android
without two teams.

Cross-platform where it makes sense, native where it does not, with the release pipeline and crash reporting set up before the first store submission.

Book a consult See our work

One codebase

Where the product allows.

Store-ready

Signing, review, release.

Crash-free

Tracked from day one.

Engagement

Built · fixed scope per increment

One codebase on iOS and Android. Works offline, syncs when back. Crash reporting live before the first store release. Example figures.

What you get.

One codebase where the product allows; native where it does not, and the decision written down

Store-ready from the start: signing, review guidelines, a release pipeline before the first submission

Crash reporting and analytics from day one, not after the first one-star review

Offline-first where the device will actually be offline

Engagement: Built · fixed scope per increment · Ask about your app →

Good for

— A web product that needs to be in the stores

— An app with more crashes than reviews

— Two native teams doing the same work twice

We will say no when

— The app is a website in a wrapper and should stay a website

— Two native teams are wanted for reasons that are not about the product

Stack · only what we have shipped to production

AndroidKotlinAOSPiOSOffline-first syncEMQX / MQTTTauri (desktop)Electron (desktop)Figma design system

Where we do this mostRetail & e-commerce →Logistics, travel & marketplaces →

From the record.

All case notes →

01 · Digital signage · SaaS

Built

Multi-tenant digital signage platform, one engineer

Problem — A company needed its own signage product: tenants, a CMS, a player it controlled, and devices that keep working offline.

What we did — Multi-tenant backend and CMS, a custom Android (AOSP) player, offline-first device sync over MQTT, an MCP-based AI concierge, credit-based AI monetisation and a white-label reseller tier, on a lean deployment stack. Architected and built by one engineer.

Measured — Live in production with its first tenant, one of Lahore’s fastest-growing restaurant chains.

Multi-tenantAOSPEMQX / MQTTMCPVercelRailwayNeonCloudflare R2

Client withheld · details on the callAsk about this →

02 · Logistics · mobile

Built

Transporter, driver and customer app

Problem — Three very different users — a transporter running finances, a driver on the road, a customer waiting — sharing one product.

What we did — iOS and Android app with a module per role: a transporter hub for loads, invoices and financial overview; a driver interface built for use in motion, with large targets and quick actions; customer visibility. A modular design system in Figma so the three stayed one product.

Measured — Fleet coordination and customer visibility improved — [ADD THE NUMBER].

iOSAndroidFigma design systemData visualisation

Client withheld · details on the callAsk about this →

03 · Retail · omnichannel

Built

Inventory, POS and quick-commerce at scale

Problem — Retailers across MENAP needed one stock position, a point of sale that worked in every store, and a mobile channel.

What we did — Distributed inventory across retailers, a cloud POS, and a quick-commerce mobile app that powered a network reaching millions of small businesses.

Measured — Distributed inventory for 60+ retailers; cloud POS in 100+ locations; a mobile channel reaching 10M SMEs across MENAP.

InventoryCloud POSMobile commerceMulti-country

Client withheld · details on the callAsk about this →

04 · AI · delivery

Data & AI

Agentic software-delivery framework on Claude Code

Problem — An engineering practice wanted to deliver faster without losing review, tests and documentation along the way.

What we did — An end-to-end pipeline on Claude Code: project planning, automated epic and story population with progress tracking, autonomous story implementation, a dedicated solutions-architect agent, guardrail enforcement, automated code review and test generation, living documentation, and human-in-the-loop escalation pushed to mobile when a decision needs a person.

Measured — Rolled out to 10 engineers and now the practice’s default path for new work. Two Android apps scoped at five developers were shipped by one, on the original timeline.

Claude CodeMCP serversAgent orchestrationGuardrailsAutomated reviewJira

Client withheld · details on the callAsk about this →

How it runs.

The same loop as every engagement

Week 0

The platform decision

What the app must do on a bad network, what it needs from the device, and who installs it.

Week 1

The release pipeline

Signing, TestFlight and Play tracks, crash reporting, analytics. Before the first screen.

Week 6

First build in testers' hands

A real journey end to end, on real devices, measured.

Then

Store submission

Review guidelines handled before review, not after rejection.

Fortnightly

The review

Crash-free rate, adoption, the next journey. Your call.

Questions we get about this.

Depends on the product, not on us. We have shipped Kotlin, custom Android (AOSP) players, and cross-platform builds; the decision goes in the SOW with the reasons.

Yes: accounts, signing, review guidelines, the release notes. If Apple rejects a build, that is our problem on our time.

Offline-first sync is something we have built for signage players that lose their connection for a week; the app keeps working and reconciles when it can.

The other seven.

All eight end in something running

01Custom software→02Team augmentation→03Data engineering & analytics→04AI & machine learning→05Cloud & DevOps→06Legacy modernisation→07Mobilehere08QA & test automation→

Mobile · the call

Tell us what the app must do offline. We will say how.

Bring the problem, not a brief. If it is outside what we do well, we will say which of our contacts to call instead.

Book a consult See our work

Or email info@hopsig.com — reply within one working day.

What you get.

One codebase where the product allows; native where it does not, and the decision written down

Store-ready from the start: signing, review guidelines, a release pipeline before the first submission

Crash reporting and analytics from day one, not after the first one-star review

Offline-first where the device will actually be offline

Engagement: Built · fixed scope per increment · Ask about your app →

Mobile app developmentiOS and Androidwithout two teams.

What you get.

From the record.

Multi-tenant digital signage platform, one engineer

Transporter, driver and customer app

Inventory, POS and quick-commerce at scale

Agentic software-delivery framework on Claude Code

How it runs.

The platform decision

The release pipeline

First build in testers' hands

Store submission

The review

Questions we get about this.

Native or cross-platform?+

Do you handle the app stores?+

What about devices that are offline for days?+

The other seven.

Tell us what the app must do offline. We will say how.

What you get.

From the record.

Multi-tenant digital signage platform, one engineer

Transporter, driver and customer app

Inventory, POS and quick-commerce at scale

Agentic software-delivery framework on Claude Code

How it runs.

The platform decision

The release pipeline

First build in testers' hands

Store submission

The review

Questions we get about this.

Native or cross-platform?+

Do you handle the app stores?+

What about devices that are offline for days?+

The other seven.

Mobile app developmentiOS and Android
without two teams.