Resources
Cross-platform mobile applications
A single codebase producing two native applications: that is what cross-platform development allows, and it is what puts a mobile project within reach of a small team. The decisions that matter concern data and the network.
What mobility changes in design
A mobile application runs in a lift, in a vehicle, in an area with partial coverage. It therefore stores locally what it needs, records the user's actions even when disconnected, and synchronises as soon as the network returns, resolving write conflicts. Add to that battery economy, permission handling and publication on stores that apply their own review delays.
- A single codebase, two native applications published
- Full offline operation, with data stored locally
- Deferred synchronisation with write-conflict resolution
- Explicit handling of the permissions requested from the user
- A release cycle that accounts for store review delays
Four structuring decisions
Where the data lives
A local database queryable offline, and a server that is authoritative. Splitting between the two is decided on day one.
When synchronisation runs
On network return, in the background, in batches. The strategy determines the user's data consumption.
How state is shared
Clear application state avoids screens showing stale data after a navigation return.
What the published version contains
A version number, release notes and a test channel: three elements that make a fix traceable.
The programmes leading to mobile development
Two paths, two depths. The first reaches a delivered product in two years, the second adds systems, networks and software engineering across three.
| Programme | Level | Duration | Credits and hours | Fees |
|---|---|---|---|---|
| Web and Mobile Development | Bachelor's degree | 2 years | 120 credits · 1200 h | 5 200 000 GNF per year |
| Computer Science programme — Bac+3 level | Bachelor's degree | 3 years | 180 credits · 1800 h | 5 400 000 GNF per year |
Questions about mobile development
Is a cross-platform app as good as a native one?
For the vast majority of business uses, the experience produced is equivalent and maintenance cost is halved. Projects that make intensive use of hardware are handled block by block, with native code where it genuinely helps.
Should I learn web before mobile?
The foundation is shared: structure, components, state, API calls. The programme builds it in that order, then adds mobile publication and device-specific constraints.
How do I handle store review delays?
By releasing in planned versions rather than fix by fix, and by using a test channel to validate before submission. The release cycle then fits the project calendar like any other milestone.
Explore next
- Designing an interfaceUser research, information architecture, visual hierarchy, component states and usability testing: the interface design method.
- Digital accessibilityContrast, keyboard navigation, screen readers, low bandwidth: accessibility checks and how to fold them into everyday work.
- Component systemsDesign tokens, component libraries, documentation and hand-off to development: building an interface system that holds at scale.
- Writing for the webWeb writing techniques: information first, headings that answer, short sentences, the words readers use, clear calls to action.
- Search visibilityKeyword research, answering content, technical optimisation and internal linking: the organic search method applied to a small company.
- Online advertisingAuction mechanics, audiences, ad creative, daily budget, attribution and acquisition cost: running a measurable campaign.