Full Stack Engineer

My Role

Frontend React Native developer and product/design consultant, contributing to:

• Cross-platform mobile development with React Native and TypeScript
• UI/UX design collaboration and implementation
• Product strategy and feature planning
• Design system development and component architecture

Technologies Used

• React Native ✓
• TypeScript ✓
• AI Integration (recipe customization)

Core Functionality

• AI-powered recipe customization for dietary restrictions
• Dietitian portal with client management and meal plan tracking
• Interactive cooking classes with step-by-step guidance
• Real-time progress tracking and analytics
• Integrated scheduling and communication tools

Core Functionalities

• Daily Themed Puzzles - New word puzzles each day from different nerdy categories
• Collectable WordCards - Each solved word becomes a digital flash card with detailed information, hints, and Wikipedia links for learning
• Progressive Hint System - Daily hints available when stuck, with Wikipedia links for deeper learning
• CDN-First Word Loading - Optimized word dictionary system with instant updates via CDN without app redeployment
• 3,800+ Word Database - Curated mix of common words (98%) and nerdy terms to create engaging gameplay progression
• Offline Support - Full gameplay available without internet connection

My Role

As the developer of NerdWord, I architected and implemented the entire application including:

• Frontend React Native/Expo development with TypeScript
• Backend Firebase Functions API development
• CDN-optimized word management system with auto-versioning
• Cross-platform deployment pipeline using Expo EAS
• Performance optimizations reducing bundle size by 243KB through CDN-first architecture
• Curated 3,800+ word database with strategic mix of common and nerdy terms for optimal gameplay

Technologies Used

• React Native ✓ (Cross-platform mobile and web)
• Node.js ✓ (Firebase Functions backend)
• Express ✓ (Backend API routing)
• Firestore ✓ (NoSQL database)
• TypeScript ✓

Additional Technologies

• React Native & Expo - Cross-platform mobile development with Expo Router
• Firebase - Backend services (Functions, Firestore, Auth, Hosting)
• CDN Architecture - Auto-versioned word dictionary with aggressive browser caching
• EAS Build/Update - Deployment and over-the-air updates
• Jest - Testing framework for component and logic validation

Tooling & Workflow

• Bootstrapped with Expo using create-expo-app (basic template)
• VS Code Chat/GitHub Copilot and Cursor for tests, refactors, semantic navigation, and safe structured edits across modules
• Figma for design system and UI component specs

Overview

NerdWord was created to combine the addictive gameplay of Wordle with educational content focused on nerd culture. The goal was to create a learning tool disguised as entertainment, where players discover new concepts from science, technology, gaming, and pop culture through gameplay.

Background

Inspired by the original Wordle's viral success, I wanted to create a variant that would appeal to tech enthusiasts, gamers, and pop culture fans while providing educational value. The challenge was balancing familiar gameplay with curated content that would introduce players to new concepts and vocabulary from nerdy domains.

Initial Designs

The initial design focused on replicating Wordle's core mechanics while adding category-based theming and educational features. Key design decisions included implementing a hint system, Wikipedia integration for learning, and a collectable card system to encourage exploration of the full word database.

Planning Process

Development was planned around three core pillars: engaging gameplay (daily puzzles with hints), educational value (detailed word information and Wikipedia links), and technical innovation (CDN-first architecture for instant content updates). The architecture was designed to support rapid content expansion without requiring app store updates.

Overview

The standout feature of NerdWord is its innovative CDN-first word loading architecture, which eliminated 243KB from the app bundle while enabling instant word updates without app redeployment. This technical innovation solved the fundamental problem of content management in word games.

Killer Feature

The CDN-first architecture with auto-versioning represents a paradigm shift from traditional app bundle approaches:

• 99.96% reduction in localStorage usage (from 243KB to ~100 bytes metadata)
• Auto-versioning system detects content changes via SHA-256 hash and increments versions automatically
• Aggressive browser caching with immutable HTTP headers and URL-based cache busting
• Zero Firestore reads for word data, eliminating database costs and latency
• Instant word updates delivered via CDN without requiring app store approval

Technical Hurdles

The main challenge was balancing performance, reliability, and developer experience. Initial approaches using Firestore generated 101,000+ reads and significant costs. The localStorage-heavy approach caused memory issues on mobile devices. Finding the optimal architecture required iterating through multiple solutions while maintaining backwards compatibility.

Solutions

The final CDN-first solution leverages browser cache efficiency, HTTP headers, and URL versioning for cache busting. Metro bundler configuration excludes word data from the app bundle, while the auto-versioning system ensures users get new content on their next session. Fallback mechanisms ensure reliability even when CDN requests fail.

Overview

Building NerdWord reinforced core architectural principles I've applied across multiple React Native projects over the past four years. The CDN-first approach validates my experience that infrastructure decisions drive performance more than code-level optimizations - a lesson learned from shipping apps at scale for portfolio companies at SecretLab.

Technical Takeaways

• Validated my approach of treating static data as infrastructure, not application state - CDN delivery eliminated operational costs while improving UX
• Confirmed browser cache strategies I've used in production apps - immutable URLs with proper HTTP headers consistently outperform application-level caching
• Applied proven React Context optimization patterns to prevent render cascades - techniques I've refined across multiple large-scale apps
• Leveraged Expo's strengths while working around platform limitations - knowledge gained from shipping both bare React Native and Expo apps to production
• Implemented accessibility-first development practices I've established as standard - WCAG compliance built into component architecture from day one

Framework Evaluation

This project confirmed my framework selection criteria developed over 4+ years shipping React Native apps professionally. I chose this specific stack - React Native/Expo with Firebase - because it's the same technology combination I've used extensively in my professional work, from early-stage portfolio companies to production apps serving thousands of users. Expo's developer experience and EAS deployment pipeline align with rapid iteration needs, while still providing escape hatches for native optimization when required. The serverless Firebase architecture scales predictably - important for portfolio company work where growth trajectories vary dramatically. Building NerdWord with this proven professional stack allowed me to focus on product features rather than learning new technologies, while also demonstrating my deep expertise with tools I use daily in client work.

Accessibility Considerations

Applied my established accessibility implementation strategy - keyboard navigation, focus management, and ARIA labels designed into the component architecture rather than added later. This approach, refined across multiple production apps, ensures compliance without retrofitting costs and provides consistent UX patterns that users can rely on.

Impact on Future Work

This project validates architectural patterns I'll continue applying to client work - particularly the CDN-first content strategy for apps requiring frequent updates without app store dependency. While this React Native/Firebase stack has proven highly effective for rapid development and scaling, I'm planning to explore SQL backends in future projects to broaden my skillset and leverage the benefits of relational databases: ACID compliance for complex transactions, mature query optimization, better data integrity constraints, and more predictable performance characteristics for data-heavy applications. The detailed analytics and user behavior tracking demonstrate the type of data-driven approach I bring to product development decisions.

My Role

I designed and developed the entire application end-to-end: information architecture, component composition, styling system, API route for email, validation, and deployment configuration. The initial template and file structure were scaffolded with Vercel's v0, then iterated in Cursor using AI-assisted refactors and safe code edits.

• Component-driven UI with reusable sections (Navbar, About, Projects, Contact, Footer)
• Form validation with Zod and client-side UX states
• Email delivery via API route integrated with Resend
• Environment-driven maintenance mode using Next middleware

Tooling & Workflow

• Vercel v0 used to generate the initial site template and component scaffolds
• Cursor for AI-assisted edits: semantic code navigation, structured refactors, and inline type fixes
• Tight feedback loop with linter/type checks to keep changes safe and incremental

Technologies Used

• Next.js 15 ✓ (App Router)
• React 19 ✓
• TypeScript ✓
• CSS Modules ✓ (scoped styling)
• Zod ✓ (form validation)
• Resend ✓ (email API integration)
• Next Middleware ✓ (maintenance mode)
• Google Fonts ✓ (Bitter)

Additional Features

• Smooth scrolling and section anchors
• Responsive layout with grid-based project cards
• Strict typing for project content data model
• Optimized images configured via Next settings (unoptimized flag for simple static hosting)

Contact Flow

The contact form uses Zod for client-side validation and a Next.js Route Handler to send emails through Resend with proper error handling and success states.

Maintenance Mode

A lightweight middleware checks an environment flag (NEXT_PUBLIC_MAINTENANCE_MODE) and redirects traffic to a dedicated maintenance page without affecting API routes.

Architecture

• App Router with metadata for SEO and icons
• Font loading via next/font with CSS variables
• Isolated CSS Modules per component for maintainable styles

Overview

Keeping content structured and typed (projects data model) reduces coupling between presentation and data, enabling easier future additions and refactors.