Back to Projects
Public-Safe Case Study
| React Native | professional

naiss ride

Public-safe case study of mobile engineering inside a live startup app: rides, feed, camera, gamification, auth, payments, reliability, and release quality.

Role
Mobile Software Engineer
Period
June 2026 - Present
Signal
Active startup work
Why it matters

Live on iOS & Android at 4.6/5 on the App Store; built the rewards & ranking engine and a full camera-capture revamp, and shipped 40+ tickets on a near-weekly release cadence.

naiss ride

naiss ride is a live social-carpooling app on iOS and Android, rated 4.6/5 on the App Store. This is a public-safe case study of the production mobile engineering behind it: shipping features across ride flows, social feed surfaces, media capture, gamification, authentication, payments, reliability, analytics, and release quality.

The work reflects real production ownership: building and leading a flexible rewards & ranking engine, a full camera-capture revamp, and a distance/streak XP system, while shipping 40+ tickets into a near-weekly release cadence - all without leaking private implementation details.

Tech Stack

React Native Expo TypeScript Expo Router Zustand NativeWind Convex Sentry PostHog Jest Detox EAS

Key Features

  • Live social-carpooling app on iOS & Android, rated 4.6/5 on the App Store
  • Built and lead a flexible rewards & ranking engine
  • Shipped a full camera-capture revamp
  • Built a distance and streak-based XP system
  • 40+ tickets shipped into a near-weekly release cadence
  • Reliability and product observability using Sentry and PostHog
  • Unit and end-to-end testing with Jest and Detox

Technical Highlights

  • React Native / Expo / TypeScript mobile stack
  • Expo Router navigation patterns for app-scale flows
  • Zustand and NativeWind usage in production UI work
  • Convex-backed app architecture exposure
  • Error monitoring and product analytics tied to release confidence
  • Mobile QA mindset across feature implementation, visual polish, and regressions

Architecture

Mobile Product Surface

  • Feature work spans high-frequency user flows rather than isolated demos
  • Navigation, state, analytics, and visual details are treated as one product system
  • Private screens and repo internals are intentionally abstracted on the public portfolio

Reliability Loop

  • Sentry for runtime visibility
  • PostHog for product behavior signals
  • Jest and Detox for confidence around unit and end-to-end paths
  • EAS for builds and over-the-air release operations

Challenges & Solutions

1

Communicating real production responsibility without exposing private product details

2

Balancing feature velocity with mobile reliability and visual quality

3

Working across multiple app surfaces while preserving consistency

4

Contributing inside an existing startup engineering workflow