Haliviq
Back to WorkGovernment & Public Sector

DITP: Public-Service Mobile App with Export Market Data

The Department of International Trade Promotion has information that businesses want in their hands, but a public-sector app is rarely a blank slate. It has to sit on top of existing government data and systems and still be easy for people who are not technical. Haliviq designed and built DITP's iOS and Android app, including the integration work that decides whether the app is useful on its first day. Screens put clarity ahead of density, content can be maintained by the agency, and the structure leaves room for new features later. Below is what we delivered and how.

Industry

Government & Public Sector

Platform

Mobile App (iOS & Android)

Year

2025

Services

4

Services Provided

UX/UI DesignMobile App DevelopmentExport Market Data SystemBusiness Database Integration
DITP

Project Objectives

  • Bring an institutional service and content set to a mobile-first public audience.
  • Connect to existing government data sources instead of duplicating them.
  • Design for a broad range of users, including people less familiar with apps.
  • Make export market data and business database information usable from a phone.
  • Let the agency keep content current without developer involvement.
  • Build a platform the agency can extend with new features over time.

What We Delivered

  • A native-feeling mobile app for iOS and Android
  • UX/UI design suited to a broad, non-technical public audience
  • Integration with existing government databases and systems
  • An export market data system presented in a readable format
  • A content structure the agency can keep current internally
  • Accessibility-conscious interface patterns
  • A secure sign-in structure for the parts of the app that need it

How We Built It

1

Stakeholder and data discovery

We mapped the systems and data sources the app needs to connect to, and who owns each of them. In public-sector work this mapping is usually where schedule and risk are decided.

2

UX/UI design

We designed for a wide public audience and chose clarity over density. Screens use plain labels, large touch targets and short paths to the information people came for.

3

Mobile app development

We built the app and connected it to the agency's existing data and systems, with secure authentication where needed. Reading from the source avoids keeping a second copy of the records.

4

Handover and extension planning

We delivered the app with a structure that the agency can extend with future features. Content management and the integration layer are documented so new work does not start from scratch.

Technology & Tools

Cross-platform mobile app framework, delivering iOS and Android from one codebaseGovernment data and API integration, reading from existing systemsCloud hosting and backend infrastructure for the appAccessible UI component library, reused across screens for consistencyContent management for agency updatesSecure authentication architecture for protected features

Results

  • The new app extends the agency's service to a mobile-first audience.
  • Data integration avoids duplicating records across systems.
  • The interface is designed for a broad, non-technical public user base.
  • The platform is structured so the agency can add new capability over time.
  • The agency maintains content internally.

FAQ

Short answers about this project.

A public-sector mobile app with system integration like this typically takes around two to three months. Access to existing data sources and the approvals around them influence the timeline most.

A cross-platform mobile app framework integrated with the agency's existing databases, deployed on cloud infrastructure with secure authentication.

Copied data goes stale and creates two versions of the truth. Reading from the source keeps the app consistent with what the agency already maintains.

We use plain labels, clear structure and interface patterns that account for accessibility. Screens avoid cramming in everything at once so a first-time user can see what to do next.

Yes. The app and its integration layer are structured for extension, so new services can be added to the same platform rather than building another app.

Yes. The data-integration and accessible-UX approach applies to other public agencies bringing services to mobile. The integration work is scoped around each agency's own systems.

Read the Full Case Study

Have a project in mind?

Let's build your next project

Talk to Us