Naiss Ride
Public-safe case study of mobile engineering inside a live startup app: rides, feed, camera, gamification, auth, payments, reliability, and release quality.
Shipping user-facing mobile features with observability, testing, and release discipline.
Naiss Ride is a public-safe case study for current production mobile engineering work inside a live startup environment. The focus is not private product disclosure; it is the engineering surface: shipping features across ride flows, social feed surfaces, media capture, gamification, authentication, payments, reliability, analytics, and release quality.
The work demonstrates the kind of execution YC and technical teams look for: moving inside a real codebase, improving user-facing surfaces, keeping quality visible with observability, and contributing to a production release cadence without leaking private implementation details.
Tech Stack
Key Features
- Production React Native and Expo feature development across core mobile product surfaces
- Ride, feed, camera, gamification, authentication, and payment flow contributions
- Reliability and product observability using Sentry and PostHog
- Quality work across unit and end-to-end testing with Jest and Detox
- EAS build and release workflow exposure in a live startup app
- Public-safe representation of private company work
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
Communicating real production responsibility without exposing private product details
Balancing feature velocity with mobile reliability and visual quality
Working across multiple app surfaces while preserving consistency
Contributing inside an existing startup engineering workflow