Software Developer
at Redime.

I helped take StaffPlus from a web app to a cross-platform attendance product used by 300+ people across 4 cities. I owned most of the product, building the React Native (Expo) app while evolving the Laravel API and React web panel behind it, so a single release cycle could touch mobile, web and backend together.

Tech-stack I’ve used here

Challenges I faced

  • Simple outside, complex inside: One tap hid a web of identification and verification flows behind the scenes.

  • Shared devices, non-technical users: Every flow had to be foolproof for untrained users on shared site devices.

  • Three surfaces, one feature: Most work spanned the Expo app, React web panel and Laravel API at once.

  • Real-world reliability: Spotty networks and daily, high-stakes use left no room for silent failures.

  • Fixing blind: Field issues had to be visible and reviewable with no developer on site.

Achievements

  • From web app to cross-platform product. StaffPlus now serves 300+ users across 4 cities on mobile.

  • Owned most of the product. ~85% of StaffPlus: mobile app, web panel, backend and product calls.

  • Weekly shipping rhythm. One release cycle shipped the Expo app, React panel and Laravel API together.

  • Hardware where it helps. NFC, camera and location became natural parts of the daily check-in.

  • Diagnostics from a desk. In-app error reporting made field issues understandable remotely.

Journey timeline

Building StaffPlus at RedimeStaffPlus grows from a web app into a cross-platform product: a web foundation (Feb–May), the mobile app built from zero (Apr–Jul), and field-hardening across all three surfaces (Aug–Oct), ending in production with 300+ users in 4 cities.FEBAPRJUNAUGOCTWeb foundationFeb–MayEmployees · attendance · reportsWeb panelAPIMobile appApr–JulCheck-in · camera · NFCMobile appField maturityAug–OctFeedback · branding · diagnosticsMobile appWeb panelAPIIn production300+ users · 4 citiesweekly releases

My approach

  • Design for the person at the door: Optimized every flow for a first-time user: big targets, clear feedback, no room for doubt at check-in.

  • Own the whole slice: Followed each feature from mobile UI to web panel to API, so all three shipped together and stayed consistent.

  • AI-assisted by default: Adopted coding agents (Claude Code) for exploration, refactors and repetitive work, sustaining a weekly cadence across three codebases without lowering the bar.

  • One small release at a time: Short weekly cycles: plan, build, test on real devices, ship. Fast feedback and small surprises.

  • Protect the critical path: Prevented double submissions and left clear recovery paths for the daily operation everyone depends on.

  • Instrument early: Instead of waiting for bug reports, the app records field failures and syncs them back for review.