C2 Capital
C2 Live
Live-streaming social app with real-time video, dynamic live layouts, and performance-sensitive interaction flows.
.webp&w=1080&q=75)
.webp&w=1080&q=75)
.webp&w=1080&q=75)
Senior iOS Developer · 10+ years of experience
Building real-time iOS experiences, reusable architecture, and polished production apps.
I build iOS applications with Swift, SwiftUI, and UIKit across social, healthcare, and AI-driven products. My work focuses on real-time systems, performance optimization, maintainable UI architecture, and close collaboration with cross-functional teams.
Selected work
Projects that reflect how I build and collaborate
These case studies highlight real-time systems, platform-minded architecture, reliability, and production ownership.
Senior iOS Developer / Team Lead
Clover
Led iOS development for a social and live-streaming app with 15M+ users, focusing on real-time features, engagement systems, and performance.
View case study →
Senior iOS Developer
C2 Capital
Built a live-streaming social platform with Swift and AgoraSDK, focusing on frame stability, reusable SwiftUI components, and dynamic video layouts.
View case study →
Senior iOS Developer
Hypercare
Built secure healthcare communication tools with strong focus on accessibility, large-data performance, and secure API integration.
View case study →
Live on the App Store
Products I’ve shipped that you can actually open
These preview images give a more visual view of the products I’ve worked on. I’m showing the strongest team-shipped apps first, followed by the independent apps I created and fully own.
Team-shipped apps
These App Store products show the kinds of production apps I’ve helped build with teams, especially in real-time and reliability-sensitive environments.
Owned by C2 Capital Inc.
Hypercare
Hypercare Messaging & On Call
Healthcare communication app with secure workflows, accessibility improvements, and reliable mobile messaging for care teams.
.webp&w=1080&q=75)
.webp&w=1080&q=75)
.webp&w=1080&q=75)
Independent apps
These are products I built and shipped myself. I own them fully and handled the product direction, implementation, and App Store release.
Jivton Inc.
Jivton
Independent product that I created and fully own, built end-to-end from product direction and iOS development to App Store release.
.webp&w=1080&q=75)
.webp&w=1080&q=75)
.webp&w=1080&q=75)
Jivton Inc.
NumberSparks
Independent educational iOS game that I created and fully own, covering product direction, design decisions, implementation, and App Store launch.
.webp&w=1080&q=75)
.webp&w=1080&q=75)
.webp&w=1080&q=75)
Yelp-targeted demo
Prototype iOS Chat SDK + Server-Driven UI demo
I designed this demo as a mini chat platform rather than a one-off chat screen. The host app launches a reusable ChatSDK, and the SDK renders server-driven message components from JSON while supporting actions, real-time updates, and SDK-level observability.
Why this demo matters
The goal of this prototype is to show that I can think beyond building a chat screen. It demonstrates how I would design a reusable iOS Chat SDK, support server-driven UI, handle conversational actions and real-time behavior, and add the reliability and observability expected in shared platform infrastructure.
Built as a reusable ChatSDK rather than a one-off chat screen, with the host app acting as a thin launcher for multiple product surfaces.
Renders conversations from JSON payloads using reusable components and a renderer registry, showing how new chat capabilities can ship with minimal client-specific code.
Includes centralized action routing, in-app business details, typing indicators, streamed assistant text, and SDK-level logs and metrics to demonstrate platform-minded engineering.
Interview context
This prototype was built specifically to match Yelp’s Chat Platform role: reusable SDK design, server-driven rendering, real-time chat behaviors, developer ergonomics, and observability at the platform layer.
iOS Chat Platform demo
Platform mindset
I think beyond features and toward systems that scale
The strongest product work usually comes from reliable foundations: reusable components, good interfaces, and code that other engineers can understand and extend.
Reusable systems
I prefer components and patterns that can support multiple features and evolve cleanly over time.
Reliability and performance
I pay attention to responsiveness, production stability, observability, and the details that shape real user trust.
Developer ergonomics
I think about how other engineers integrate, extend, and maintain the code—not just how a feature looks on day one.
Working style
How I approach engineering with teammates
I value calm execution, clear communication, and thoughtful tradeoffs—especially when systems are complex and multiple teams are involved.
Collaborate early
I work closely with product, design, and backend partners to make scope, tradeoffs, and constraints visible.
Own outcomes
I like taking responsibility for feature quality end-to-end, from architecture and implementation to polish and follow-through.
Keep complexity readable
I try to make difficult systems understandable through clean APIs, structured code, and calm communication.
Contact
Interested in working together?
I’m happy to discuss iOS architecture, real-time systems, reusable mobile platforms, and engineering collaboration.