Two-sided local hiring marketplace with in-app QR signage generation and printing
A React Native marketplace app with two complete experiences in one binary — local businesses post and manage jobs, review structured applications and print QR-coded signage from inside the app; job seekers browse nearby roles, build a reusable profile, and apply in minutes by scanning that signage.
Local hiring runs on a card in a shop window — visible only to people already walking past, producing no record, interrupting the business at the worst moment. Job seekers had no way to tell who was actually hiring, since mainstream job boards are built for salaried professional recruitment and serve hourly, local roles poorly. The product also had to serve two completely different audiences from one budget, and it had started life as two separate native codebases that were falling out of step release to release.
Built a role-resolving application shell: after authentication, the app determines which side of the marketplace the user belongs to and mounts an entirely separate navigation tree, home screen and feature set, while both sides share the component library, networking layer and utilities underneath. Rather than treating the QR bridge as a marketing add-on, built the whole loop client-side — a business generates its code, composes it into printable signage on the device via view capture, prints or shares it directly, and the resulting scans come back as recorded visitors, with no back-office print pipeline required.
Having originally shipped as separate native iOS and Android apps, rebuilt the product as a single React Native codebase against the existing API contract, holding feature parity — camera, maps, geolocation, file handling, printing, push — as a hard constraint. Multi-language support, including a right-to-left language, was designed in from the start rather than retrofitted, and over-the-air update delivery lets fixes reach users without waiting on app-store review.
Businesses reach candidates beyond passers-by while still capturing the ones they were already getting, because the shop window itself became a working entry point into the platform. Applicants arrive as structured profiles with work history and a CV instead of interruptions, and consolidating from two native codebases into one cross-platform build roughly halved the cost of every feature going forward.
Something holding you back?
New build, rebuild, or adding AI to what you already have — I'll take a look and give you an honest perspective.