Mobile apps
Android: on Google Play (1.0.0). iPhone and iPad: on the App Store (1.0.0). Without the app, the web app works on phones too, with a bottom tab bar for employees.
The native apps are open source, in the same repository: iOS in SwiftUI (apps/ios) and Android in Kotlin and Jetpack Compose (apps/android). Both are built and tested against a real Crow HR server. On an iPad the iOS app shows a sidebar in landscape and can share the screen in Split View, Slide Over and Stage Manager.
The apps cover what employees and managers do most: payslips, leave, clock in and out (also offline), claims with a photo of the receipt, your schedule, approvals and notifications. Everything else stays on the web.
Try it with a demo company
Section titled “Try it with a demo company”You don't need a server of your own to try the app. Open the try page on Crow Tech's demo server and tap Start my demo company.
You get a private copy of Kopi Kaki, the fictional café group from the demo, with four months of payroll, leave, claims and rosters. Then open it:
- on your phone: tap Open in the Crow HR app (on Android it opens Google Play if the app isn’t installed yet; on an iPhone or iPad, install it from the App Store first);
- on a computer: scan the QR code with the app or the phone’s camera;
- in the browser: Open in this browser, on the same company.
Sign in by picking a person, with no password: Hafiz (Employee), Siti (his manager), the HR admin, the payroll admin or the owner. Everyone sees what their role allows, so you can apply for leave as Hafiz on the phone and approve it as Siti in the browser. The app labels the server as a demo server with fictional data.
Your demo company is yours alone (its short name, demo- and 12 characters, is the key to it) and is deleted with everything in it 3 days after you start it. The try page keeps it for you in that browser until then. In a demo company, sign-in and security settings, invitations, passwords and email are switched off, and uploads are limited to 25 MB. The app doesn’t upload photos to a demo company, so receipts there are added in the browser. Each network can start a few demo companies an hour, and the server a few dozen. Nothing is retained: what you enter stays in your demo company until it ends and is then deleted with it, and the start limits keep only a count per network (not its address) for at most a day.
Running your own demo server? See demo companies in the configuration reference.
How the apps connect
Section titled “How the apps connect”The apps connect only to your company’s own Crow HR server. Crow Tech runs no server for them, and they collect no data: no analytics, crash reporting or third-party SDKs. The apps’ privacy policy and support page are on crow.sg, where the store listings link.
Each person finds their connection code in My profile → Mobile app:
- a QR code to scan with the app. It holds
crowhr://connect?server=<your PUBLIC_URL>&org=<organisation>and nothing else: no password, session or token, so it is safe to show on screen or print for a notice board; - the server address (your
PUBLIC_URL) to type into the app instead, with a copy button, and the organisation’s short name; - links to the app on Google Play and the App Store.
If you type the address and the server hosts more than one organisation, the app also asks for the organisation’s short name (its ID). The app then checks the server, shows your organisation’s name for you to confirm, and signs you in through your phone’s browser with the same methods you use on the web (password, Google, Microsoft, Singpass or your identity provider).
The app needs HTTPS. On a plain-HTTP server (a LAN install without a certificate), My profile says so: the app will connect over HTTP only to a private network address or a .local name, after warning that the connection is not encrypted. See reverse proxy to add HTTPS.
On Android 17 and later, connecting to a server on your office network (a private address such as 192.168.1.20) also needs the local network permission; the app asks for it before connecting. A server with a public HTTPS address needs no extra permission.
Clocking in offline
Section titled “Clocking in offline”A clock-in made without signal is saved on the phone and sent when it reconnects. The app sends the tap time and how long ago the tap was, measured by the phone’s own timer, which changing the phone’s clock doesn’t affect. So the server records the real time even if the clock was changed while offline, flags a wrong phone clock as clock skew, and marks punches that arrive more than 10 minutes late as sent late. Punches more than 7 days old are refused, as on the web; the app keeps them visible with the server’s reason so a manager can add the time to the timesheet.
The server side the apps use is part of every install: native sign-in with PKCE and device sessions (listed in My sessions, where you can sign a device out), GET /api/v1/meta for the organisation’s name, logo, sign-in methods and features, and GET /api/v1/notifications?since=<cursor> for background refresh (API conventions). The apps check the server’s features rather than its version, so they keep working with servers older than the app.