Fuyu Labs: Rapid Product Development

Building and Shipping 3 Consumer Apps Through Iterative Product Development

Role
Founder & Product Builder
Timeline
Dec 2024 - Present
Apps Shipped
3 Products
Focus
Product Strategy & Execution
See the Results →

Product Development Approach

Rapid Product Iteration

Built and shipped 3 consumer applications in 3 months to rapidly validate different product approaches and development methodologies. Each product taught different lessons about technical constraints, user behavior, and product-market fit.

Sunset
Lively (Web)
Social goal and habit tracking platform. Pivoted away due to maintenance complexity, security concerns, and unclear monetization path.
Live on App Store
Lotus (iOS)
Digital wellness app with screen time blocking and habit-building games. Learning about focus and feature scope the hard way.
Live on App Store
BambooReader (iOS)
Chinese reading app for improving literacy. Built faster than Lotus while waiting for App Store approval. Planning Apple Intelligence integration.
In Development
Developer Tools
Exploring automation tools for iOS development workflows. Early experiments with improving developer productivity through AI-assisted development processes.

Product Development Methodology

Prototype-First Product Development

I validate ideas through rapid prototyping rather than extensive planning. This approach reveals user needs and technical constraints quickly, enabling faster iteration and more informed product decisions.

Systems-Level Product Thinking

I approach products from a systems perspective, mapping relationships between features and user workflows. This helps with strategic product decisions while sometimes requiring focus to prevent over-engineering.

AI-Assisted Prototyping

Claude helps me translate conceptual ideas into working code quickly. This accelerates learning and lets me test assumptions through actual functionality rather than mockups.

Learning Through Making

Coming from biomedical engineering, building software feels similar to prototyping physical devices - you discover constraints and opportunities through the act of building.

Product Challenges & Solutions

Lively: Monetization Reality Check

Originally planned a complex network effects model with user engagement features. Realized the path to revenue was too long and uncertain. Learned that subscription models are more predictable for solo founders.

Lotus: Technical Constraints Hidden Until Late

Built multiple features before discovering Apple's Screen Time API limitations for family sharing. The permissions I needed weren't available for distribution, only development. Now I check technical feasibility first.

Lotus: Over-Engineering from Excitement

Added too many habit-building games because I was excited they were working. The app became overwhelming with too many features. Learning to validate core functionality before adding variety.

Data Storage Surprises

Spent time building features with one storage approach before realizing I needed Core Data for persistent storage. iOS development has more gotchas than I expected coming from web development.

Key Product Insight

Shipping multiple focused products teaches more about product development than building one complex product. Each application highlighted different aspects of user behavior, technical constraints, and business model validation.

Product Development Timeline

Iterative Product Development

Dec 2024

Lively (Web App)

Started with social goal tracking. Learned about user authentication, real-time data, and the complexity of building secure web applications. Realized maintenance burden was too high for solo development.

Jan 2025

Pivot to iOS with Lotus

Switched to iOS development for better security and simpler deployment. Built digital wellness app with screen time blocking. Discovered Apple's API limitations and over-built features from excitement.

Feb 2025

BambooReader While Waiting

Built Chinese reading app while Lotus was in App Store review. Moved much faster on second iOS app, applying lessons about scope and technical validation from Lotus experience.

Current

Xcode Automation Tool

Experimenting with MCP server to automate development workflows. Building tools to help Claude directly modify Xcode projects. Early proof of concept working.

User Research & Validation

Friends & Network Testing

  • Showed apps to about 15-20 people across all projects
  • Watched them use the apps rather than asking structured questions
  • Focused on observing behavior and confusion points
  • Used feedback to prioritize bug fixes and UX improvements

Community Research

  • Read Reddit and Discord discussions about language learning and digital wellness
  • Analyzed what people complained about in existing apps
  • Studied which features successful apps kept vs. removed over time
  • Looked for patterns in user requests and complaints

Personal Use Cases

  • Built apps for problems I personally experienced
  • Used my own apps daily to identify friction points
  • Started with features I would actually pay for
  • Tested assumptions through my own usage patterns

Build-to-Learn Strategy

  • Shipped minimal versions quickly to get real feedback
  • Used App Store reviews and user behavior as validation
  • Focused on one core feature per app initially
  • Let usage data guide feature prioritization

Product Development Insights

Technical constraints surface late in mobile development
iOS has many API limitations and permissions that aren't obvious until you try to implement them. Now I validate the core technical feasibility before building features around it.
Excitement leads to over-building
When features work well during development, it's tempting to add variations and complexity. But users often prefer focused functionality over comprehensive feature sets.
Platform choice affects everything
Moving from web to iOS changed my development speed, security concerns, monetization options, and user expectations. Platform constraints can actually improve product focus.
Building multiple products teaches different lessons
Each app highlighted different aspects: Lively taught me about monetization models, Lotus about technical validation, BambooReader about development speed. Variety accelerated learning.
AI assistance changes development workflows
Using Claude to translate ideas into code lets me focus on product decisions rather than syntax. This is especially valuable when learning new platforms and frameworks.
User feedback through observation beats surveys
Watching people actually use apps reveals confusion points and workflow issues that they wouldn't think to mention in conversations. Behavior is more honest than stated preferences.