←BaldanAll skillsLet's talk

Web, SaaS & Mobile · Mobile lab

Apps that live in a pocket.

A phone app works with a weak signal, gets closed and reopened all day, and is woken by messages from far away. Here is how that works, with two phones you can take offline, an app you can push to, and the real sensors of the device you are holding.

01 · Ways to build

Four ways to turn code into an app.

Each one gets code onto the screen differently, and that one choice decides speed, cost and who you hire. Watch each pipeline, compare them, then answer four questions.

01

Native

Swift (iOS) and Kotlin (Android)

Swift · Kotlintwo codebasesCompilerXcode · Android StudioNative UIUIKit · Composebuild
1/3

Each platform gets its own app, written in its own language.

02

React Native

React + TypeScript, usually with Expo

React (TS)one codebaseJSI bridgetalks to nativeiOS viewsreal UIViewAndroid viewsreal android.view<View />
1/3

You write React components in TypeScript.

03

Flutter

Dart

Dart widgetsone codebaseFlutter engineImpellerPixelsdrawn by Flutterwidget tree
1/3

You describe the screen as a tree of Dart widgets.

04

Installable web app

HTML, CSS, JavaScript (a PWA)

Web appHTML · CSS · JSService workeroffline cacheBrowser engineHome screeninstalled iconopen URL
1/4

It starts as a website, no store needed.

rule of thumbNativeReact NativeFlutterInstallable web app
Performancebestvery goodvery goodgood
Code shared by iOS and Androidnone: two appsmost of itmost of itall: one web app
Device featureseverything, firstnearly all (+ native modules)nearly all (+ plugins)limited, especially on iOS
In the app storesyesyesyesoptional
Shipping an updatestore reviewstore review, or over-the-air for JSstore reviewinstant on deploy
Team you neediOS + Android developersReact / TypeScript developersDart developersweb developers

Do you need the deepest device features or top performance (AR, heavy animation, long background work)?

One small team for both iOS and Android?

Must it be in the App Store and Google Play?

Does your team already build web apps with React?

Your fit

Answer a question or two and the best fit lights up above.

02 · Offline-first sync

Two phones, one list, no signal.

Field apps save to the phone first and sync later. That's easy until two people change the same thing while offline. Take the phones offline, edit, bring them back, and pick how the server settles it.

When two edits collide:
Rina's phoneonline

Visits today

all synced ✓

Server · the source of truthclock t0

Visit Toko Sinar

text: original t0 · done: false by original t0

Restock coffee beans

text: original t0 · done: false by original t0

Send invoice to CV Abadi

text: original t0 · done: false by original t0

Sync log

  1. Both phones are online and in sync.
Budi's phoneonline

Visits today

all synced ✓

Simulated in your browser. Try it yourself: put both phones offline, rename a visit on Rina's phone, tick the same visit on Budi's, then bring them back. With “merge per field” both changes survive; with “whole item” the later save wins and the other edit vanishes, which is why serious offline apps track changes per field (or use CRDTs).

03 · Push & lifecycle

What happens when the app is closed.

Apps are opened, sent to the background, frozen and killed all day, and a push behaves differently in each state. Move the app through its lifecycle and send it messages.

09:41

Kirim

Kirim is not running

Your server sends a push:

The app's lifecycle

Not runningno memory usedForegroundon screenBackgroundrunning, brieflySuspendedfrozen in memoryopenhomebacktime passesresumeswipe awaykilled

What your code hears

Open the app, send it to the background, wait, and send pushes in each state. Each move shows the callbacks every platform fires.

How a push travels

Your server never talks to the phone directly: Apple and Google keep the one connection open.

Phoneapp closedYour serverAPNs / FCMApple · Googledevice token
1/3

With permission, the app registers and sends its device token.

Real, in this browser

Switch to another tab or minimise the window, then come back. A web page has a lifecycle too.

Times you left this tab

0

Notification permission

…

    04 · Device APIs

    What your phone can tell an app.

    Read live from the device you're using right now. Open this page on your phone for the full set.

    – of 9 available in this browser

    ScreenLanguage & timeConnection detailsBatteryLocationMotion sensorsVibrationShare sheetKeep screen on

    Screen & input…

    Layouts that fit, sharp images, big touch targets for fingers.

    Language & time…

    Dates, numbers and money in the user's own format.

    Network…

    Go offline-first, send smaller images on slow links.

    Battery…

    Pause heavy work when the battery is low.

    Location…

    Delivery tracking, nearby stores, check-ins at a visit.

    Your browser asks you first. Shown here rounded to about 1 km, never sent or stored.

    Motion sensorson tap

    Games, step counters, rotating maps, shake-to-undo.

    Tilt front/back
    0°
    Tilt left/right
    0°
    Compass heading
    –

    Vibration…

    A buzz to confirm a scan or warn of an error.

    Share sheet…

    Send a link to WhatsApp, email or any app, with the system's own sheet.

    Opens the same share sheet native apps use, with this page's link. You pick where it goes, or cancel.

    Keep screen on…

    Recipes, navigation, a driver's delivery list.

    Stops the screen from dimming while this page is open. Released automatically when you leave.

    Everything here is read by your browser on this page only: nothing is sent or stored. Native apps get more (contacts, Bluetooth, NFC, background location, health data), each behind its own permission prompt; web pages get a careful subset, and Safari offers the fewest.