Flutter App Development
Flutter cross-platform applications and unified business operations
For camera scanning, Bluetooth printing, location services and push notifications in retail, logistics and property management, native iOS capabilities are designed and integrated through the relevant system interfaces. Permission scope, device compatibility and acceptance criteria are defined at the start of the project.
If your team skills or feature list do not quite match this page, compare it against the other two routes before deciding.
Flutter cross-platform applications and unified business operations
React Native cross-platform applications and existing system integration
The activities below are the ones we own on this type of project, delivered in phases and confirmed item by item. Where third-party hardware or licences are involved, the procurement list, licensing requirements and responsibility split are set out at solution stage.
Native Swift and SwiftUI screens, navigation and state management
Camera, Bluetooth, location, push notifications and biometric authentication
Backend API integration, local caching and weak-network retry
App Store submission pack, review follow-up and release cadence
Crash monitoring, OS version compatibility and feature iteration after launch
Every item is archivable and transferable, so an internal team or a third party can maintain the system later.
Selected against the existing environment and the capabilities of your team, with maintainability and future extension in mind.
Each phase produces a confirmable output and an acceptance record, so issues are resolved within the phase.
Phase 01
Agree first-phase screens, the system capabilities they need and the matching permission copy
Phase 02
Clickable prototype and visual design covering empty states, error states and first-run guidance
Phase 03
Module-by-module delivery, tested on real devices across current iOS versions, then TestFlight beta
Phase 04
Submit for review, address rejections, then plan releases against crash and usage data
For iOS App Development, the requirements below directly affect data structures, page behaviour and deployment. We confirm each item during solution design; formal legal advice should be confirmed with a local adviser.
The Ordinance sets six data protection principles covering purpose and manner of collection, accuracy, retention, use limits, security, and access and correction rights. The 2021 amendment criminalised doxxing. Systems are designed with consent records, retention limits and permission auditing. Section 33 on cross-border data transfer has not been brought into effect; cross-border transfers are handled according to the contract and the client's requirements.
The Ordinance gives electronic records and electronic signatures legal effect, providing a basis for electronic contracts, e-signature and online confirmation flows. Where signature is involved we follow the client's legal advice on the method, and keep timestamps and action logs inside the system.
The Ordinance prohibits unfair trade practices including false trade descriptions, misleading omissions and aggressive commercial practices, and applies to prices, promotions and performance claims on websites and campaign pages. Page copy is written against verifiable facts, with the applicable conditions of each price and offer stated.
Where cards are accepted, card numbers and verification codes never enter our database: a licensed payment institution processes them and the system stores only the transaction reference and status. Local methods such as FPS, PayMe and Octopus are integrated through their published interfaces, with callbacks and reconciliation records kept in traceable logs.
The first three answers are general; the last two address conditions specific to Hong Kong.
Native is the safer choice where the app leans on system capabilities, complex gesture animation or demanding rendering. Where the work is mostly forms, lists, messaging and payments, cross-platform cuts the cost of maintaining two codebases. We assess your feature list before recommending, rather than applying one rule to every case.
Yes. Rejections usually trace to permission copy that does not match actual use, a missing privacy manifest, no account deletion path, or virtual content that bypasses in-app purchase. We work through the review guidelines item by item and attach an explanation with the resubmission.
We run compatibility regression on each major iOS release, checking safe areas, navigation bars and permission dialogs. Compatibility fixes are usually covered in the first year; after that they can sit under an annual maintenance agreement.
Meetings and confirmation points follow the working hours common in Hong Kong (UTC+8, the same time zone as Hong Kong with fully overlapping working days). Requirements and solution design include a written progress update every week; development delivers a runnable build every two weeks. For cross-timezone work, key confirmations are placed inside the overlap of both working days, so progress never stalls waiting on a reply.
Projects in Hong Kong typically involve Personal Data (Privacy) Ordinance (Cap. 486), Electronic Transactions Ordinance (Cap. 553), Trade Descriptions Ordinance (Cap. 362). These requirements directly shape data structures, page behaviour, hosting location and data retention, so each is confirmed at solution stage and recorded in the delivery documentation. Formal legal advice should be confirmed with a local adviser.
Most projects combine two or three services, for example a website followed by a business system, or AI capabilities added after a system goes live.
Business rule configuration and custom software development
Front-line mobile applications and offline data synchronisation
Traditional Chinese and English website development
Multi-store, multi-currency and multi-entity financial management
IoT pilot validation and multi-site deployment
Source-backed intelligent Q&A and human support