Our entire engineering team consists of just two people: one mobile engineer and one backend engineer.

The Vision: Moving Beyond Swipe Fatigue

Most modern discovery apps rely on endless profile swiping, which often leads to disengaged users and dead-end conversations. We wanted to design an experience centered around real-world intent:

• Discovery is driven by immediate geographic proximity and shared plans rather than arbitrary photo browsing.

• Interactions are time-sensitive, encouraging real-world meetups rather than endless digital pen pals.

The Two-Person Division of Labor

Building a real-time mobile product with two developers requires clear boundaries and zero unnecessary meetings:

• Mobile (Client Side): Focused entirely on delivering a smooth user experience.

• Backend (Server Side): Focused on database integrity, security, and the core matchmaking engine. Every incoming request - from searching active plans in a specific radius to managing active subscriber states - had to run reliably with minimal latency.

Handling Complex Logic on a Lean Footprint

Despite keeping our technology concepts straightforward, social apps come with inherent structural complexity:

• Live State & Notifications: Balancing invites, real-time chat status, and countdown timers requires a synchronized state machine so users never see outdated plans or ghost profiles.

• In-App Monetization: Creating a hybrid model of weekly/monthly subscriptions and consumable boosts meant designing clear logic triggers that respect user limits and provide instant access upon checkout.

Lessons from Shipping Fast

Building with two engineers forces ruthless prioritization. If a feature does not directly help users find a companion or plan an activity faster, it gets cut. By focusing purely on core product mechanics and keeping our systems simple, we were able to launch an active, revenue-generating app without unnecessary bloat.

You can see the final result live on iOS and Android at Bfriendz.