Front-end developer with UI design skills: React web + Expo app

PocketMode is an Australian start-up building workforce management for outdoor crews, starting with farms. Workers use a phone app to see their roster, clock in and out, and get heat alerts. Managers use a web dashboard to roster, approve timesheets and leave, and manage locations. The product works end to end. It doesn't yet look or feel like something a farm manager would trust with their payroll, and that's this job. **What exists today** - Web dashboard: React 19, TypeScript, Vite, Tailwind 4, Ant Design 6, Redux Toolkit Query, React Router 7, Recharts, Leaflet and MapLibre. - Worker app: Expo SDK 54, React Native 0.81, TypeScript, React Navigation 7, Redux Toolkit, i18next, Firebase push. - API: Node, Express and MongoDB, documented in Swagger. Our existing developers own the API and the phone's sensor and background code; you won't build backend. - A complete first-pass design set for every screen already in the code, about 110 screens across both apps, with brand tokens, components, copy, empty and error states, and engineering notes. They're HTML boards, not Figma. A second set covers features still waiting on the API. **The job** Phase 1, the main piece of work: 1. Review the designs with me and improve them: usability, consistency, accessibility, small phones and laptop widths. Work in Figma or straight in code, but I see and approve changes before they're built. 2. Build them into the existing web and mobile code against the existing API, including loading, empty, error and offline states. 3. Tidy what's there: leftover template text, copy that doesn't match, and validation rules that differ between the two apps. On the phone: sign-in and password flows, home and shifts, clock-in with a per-shift tracking question, activity charts, leave, notifications, profile and settings. On the dashboard: the roster and shift editor, timesheets, employees, managers and users, locations with a map pin, announcements, a question library, settings and heat alerts. Phase 2, if Phase 1 goes well: refine and build the next features as their APIs land, such as breaks, shift questions, open shifts and swaps, safety reports, pay and reports. **You're right for this if you** - have shipped a React Native app to the App Store and Google Play (Expo preferred) - have built a data-heavy React web app: tables, filters, drawers and forms - can show a screen you designed and then built, and explain what changed between the two - write tidy TypeScript in small pull requests and test on real phones, including mid-range Android - care about contrast, touch targets and screen readers, and about the words on the screen - can overlap at least 3 hours a day with Sydney time (UTC+11), Monday to Friday Nice to have: Ant Design theming, Tailwind, Leaflet or MapLibre, Android permissions and battery optimisation, i18n, rostering or field-worker apps. **How it works** - A paid, fixed-price trial first: the Leave screens on both the dashboard and the app, built against the existing API. About 15 to 20 hours of work. - Then milestones by screen group, each ending in a short demo on staging. - Pull requests on GitHub, reviewed before merge. - A short NDA and IP assignment before you get access to the code and designs. **To apply** Start your proposal with the word "paddock". Then, in a few lines: an app you've shipped (store links), a dashboard you designed and built, how you'd approach Phase 1, and roughly how long you'd expect it to take. --- **Screening questions** 1. Give an App Store or Google Play link for a React Native app you worked on, and say what you built in it. 2. Show a screen you designed and coded yourself. What changed between the design and what shipped, and why? 3. A design shows a feature the API can't support yet. What do you do? 4. How do you handle loading, empty and error states on a table that pages from an API? 5. How many hours a week can you give this, and which of them overlap with 9 am to 5 pm Sydney time?