Workforce Management Platform (App, Web Dashboard, Kiosk, Offline-Functionality)

READ FIRST: Do not apply if you will be writing your response with AI, we will ignore it. We are not new to hiring developers. Do not apply if you will primarily be using Codex, Cursor, or Claude Code to develop this. We are also familiar with these tools and will not hire you. Experience with Fully Kiosk Browser, clock-in/clock-out platforms, employee management systems, and offline-first applications is preferred. Do not apply if your portfolio is AI slop. Applicants who create a Loom will be prioritized. This should be a simple project for an experienced developer. No more than 20-40 hours. We’re building a workforce management platform for our multi-site retail business, essentially our own version of Homebase (https://www.joinhomebase.com/) focused primarily on timekeeping, kiosk reliability, time entries, and payroll. We already built the first version in Lovable. The UI/UX, workflows, and overall flow are exactly how we want them. The problem is the underlying architecture and reliability. Our first version works perfectly for now. We just need someone to come in and polish it into a real production-ready MVP. Our stores currently use tablets running Fully Kiosk Browser connected to the site as employee time clocks. If a kiosk loses internet connection, we cannot risk clock-in or clock-out data being lost. This is the main technical problem we need solved properly. We also want to move away from relying solely on Fully Kiosk Browser. The employee clock-in kiosk should ultimately be packaged as an installable tablet app for iOS/iPadOS and/or Android through the Apple App Store or Google Play Store. The kiosk app should connect to the same backend as the management website while maintaining its own reliable local/offline storage. What we want: * Migrate the existing platform off Lovable and rebuild it as a production-grade application. * Host the management platform on our own website/VPS or another architecture you recommend. * Supabase will be used for the database/backend if appropriate. * Preserve the existing UI/UX and workflows as closely as possible. The current Lovable platform will serve as the functional reference. * Build the clock-in/time-clock portion as an installable iOS/iPadOS and/or Android kiosk application. * Handle the setup required to distribute the kiosk app through the Apple App Store and/or Google Play Store. * The kiosk app and web dashboard should use the same backend and stay synchronized. The main focus is the kiosk/time-clock system: * Employees clock in and out from a tablet kiosk using a PIN. * The kiosk should run as a dedicated installed application rather than depending entirely on a browser session. * We are open to native or cross-platform development as long as the result is reliable. * The app should support iPads/iOS and/or Android tablets, with App Store or Google Play distribution. * The kiosk should stay authenticated to its assigned store/site without employees needing to log into the device. * Punches need to be recorded instantly. * If the store loses internet, punches must still be saved locally on the kiosk. * The offline functionality must work at the application/device level, not depend on an active connection to Supabase. * When internet returns, punches automatically sync to the server. * No punch can be lost. * No punch can be duplicated if the kiosk retries a sync. * The system should know which punches are still waiting to sync. * Management should be able to see kiosk connectivity/sync issues. * We want reconciliation so the server can verify that everything recorded on the kiosk made it into the database. * If a kiosk is offline for several hours, employees should still be able to clock in and out normally. * Once connectivity returns, the app should reconcile its local records with the server automatically without requiring employee or manager intervention. Time entries are the source of truth for payroll: * Every clock-in and clock-out creates the employee’s time entries. * Managers can review and edit time entries. * Manual edits require a reason/note. * Missed clock-outs should be flagged automatically. * We currently use an 11-hour threshold to identify likely missed clock-outs (someone is clocked in too long). * Payroll should not be considered complete while unresolved time-entry issues exist. * Full audit history should show what was changed, when, and by whom. Payroll should automatically calculate from approved time entries: * Employee hours roll directly into payroll. * W-2 employees have our specific payroll buckets such as REG, MEAL, WEEKEND, etc. * 1099 employees use the applicable simpler calculations. * Pay rates are stored per employee profile. * Payroll totals should require no manual math. * Payroll calculations need automated tests so the same inputs always produce the same expected output. * Export should match the format we use for ADP so payroll entry is fast and straightforward. * Historical payroll and time-entry data needs to remain accessible. Other core requirements: * Multiple business locations/sites (tenant-based). * Employees assigned to one or more sites as needed. * Owner/manager/back-office permissions (RBAC). * Secure employee PINs. * Clear dashboard showing who is currently clocked in, current hours, payroll totals, and anything requiring attention. * CSV/PDF exports where needed. * Immutable audit history for sensitive changes. * Initial migration/import of our existing employees, sites, time entries, and payroll records. The current product already exists in Lovable and can be demonstrated end-to-end. We are not looking for someone to reinterpret the product or redesign everything. We need someone who can look at the working reference, understand the workflows, and engineer the production version correctly. Most importantly, we are not looking for someone whose development experience consists primarily of using Claude Code, Codex, Lovable, Cursor, or similar tools to assemble applications. Using AI tools as part of development is completely fine, but we need an actual senior developer or small senior team who understands: * Offline-first architecture * Local persistence * Native or cross-platform mobile/tablet development * iOS/iPadOS and/or Android application deployment * App Store / Google Play release processes * Sync queues * Idempotency * Deduplication * Conflict handling * Database architecture * Supabase/Postgres * Authentication and permissions * Production deployment * Payroll/timekeeping systems * Reliability testing You should be able to explain exactly what happens technically when a kiosk loses internet, an employee punches out while offline, the device reconnects two hours later, and the sync request gets retried multiple times. The goal is straightforward: take the Homebase-style platform we already validated in Lovable and turn it into a reliable production system we can run across all of our stores without worrying about losing punches or calculating payroll incorrectly. The management side should live on the web, while the store time clock should be a reliable installed tablet application that continues functioning even when the store has no internet.