Contact
Case study Community platform for luxury watch trading

How we helped a luxury watch community go independent and safer

A 4K+-member Facebook group moved to its own platform on web, iOS and Android — real-time chat, real moderation tools, and no custody of funds.

Under NDA: client and product names are omitted; screenshots are illustrative only.
4K+ members in the seed group
2,000+ real users after rollout
200–300 daily active members
~5 mo from zero to shipped MVP
Industry
01
Luxury watch trading
Platforms
02
Web, iOS, Android
Timeline
03
~5 months to MVP
Team
04
9 specialists
The challenge

Real-time community, strong moderation, no payment custody

Our client needed a partner to build the product from scratch on a tight timeline, with Kotlin Multiplatform chosen to support a cross-platform app. The goals were clear and non-negotiable:

Familiar by design Keep the UX familiar and fast for seamless migration from Facebook.
Chat without a full SPA Ship real-time chat without the weight of a full SPA.
Trust and safety enforced Enforce Trust & Safety with roles, pre-moderation, strikes, and verified dealers.
No funds on the platform Stay out of payment custody; allow P2P coordination off-platform and use subscriptions for premium.
The mission

Give members a home that feels familiar, but runs by their rules — a shared platform where multiple watch communities can come together and grow into a central hub for discussion and culture.

Pre-moderation pipeline
Listing submitted Member posts a watch 01
Pre-moderation Held before it goes live 02
Moderator decides Approve, edit or strike 03
Live in the feed DM the seller from it 04
3-strike policy · verified dealers only for sales
The process

From zero to platform in ~5 months

The real challenge was not speed, but building an experience good enough that watch enthusiasts would actually leave familiar Facebook groups. We started with a one-month inception to lock scope and architecture around “Facebook-level comfort with better tools,” then ran short sprints to ship an MVP across web, iOS, and Android that felt like a credible, if not better, home for these communities.

One month to resolve ambiguity

We ran a focused one-month inception to kill ambiguity and lock a buildable MVP. Together we produced:

  • A Functional Requirements document with a clear scope.
  • Full-app wireframes and several design concepts for the client to choose from.
  • A CI/CD pipeline with smoke tests and a biweekly demo cadence.

This rhythm kept decisions quick and rework to a minimum. We captured ~20 demo recordings to document choices and de-risk the next sprints.

Inception timeline4 weeks
ScopeWeek 01FRD signed off
WireframesWeek 02full app flow
ConceptsWeek 03client picks one
CI/CDWeek 04smoke tests live
Biweekly demos from week two · ~20 recordings captured
Team & process

Cross-functional, transparent, fast

A 9-person team drove delivery: PM, BA, UI/UX, Backend, Frontend, Kotlin, iOS, Android, 2 QA. We worked in short sprints with biweekly demos, clear hand-offs, and documentation that your team can own.

Product3 people PMBAUI/UX Owns: FRD, wireframes, design concepts
Web2 people BackendFrontend Owns: API, feed, chat integration
Mobile3 people Kotlin / KMPiOSAndroid Owns: KMP core, SwiftUI and Kotlin UIs
Quality2 people QAQA Owns: smoke tests, regression, releases
Roadblocks

Overcoming roadblocks

Real-time UX without a heavy SPA We kept the web app server-driven and scoped React to chat. You get fast loads, simpler caching, and lower upkeep.
Trust & Safety at scale We implemented role-based controls, pre-moderation, and a strike system, plus “Dealer” role verification. Moderators get practical tools and basic analytics to keep the community clean.
Cross-platform consistency KMP shares domain logic across iOS and Android. SwiftUI and Kotlin deliver native UIs with the same behavior — fewer surprises and faster iteration.
Payments separation The platform never holds funds. Members coordinate P2P off-platform, while subscriptions unlock premium — less compliance drag, more focus on community value.
Frictionless migration from Facebook We mirrored familiar patterns, added listing presets, and enabled DM from a post. Members feel at home on day one.
Facing the same roadblocks? Tell us where your community is stuck — moderation, chat load, payments, migration — and we will map the shortest path to a platform you own. Discuss your case
Results

A stable, trust-first community platform

Pre-release, with the first Facebook cohort already migrated and the platform now operating under the community’s own rules.

Predictable team and planningEven as the vision expanded, team size and composition stayed dynamic instead of freezing scope — 1-month inception plus ~3.5–4.5 months of build, inside the ~5-month timeline. ~5 months end to end
Transparent progress~20 demo recordings, an FRD, architecture notes and Figma keep everyone aligned. ~20 demo recordings
Lower TCOServer-driven web avoids SPA bloat; React is isolated to chat. React only in chat
Risk under controlNo custody of funds; moderation and dealer verification strengthen safety. Zero custody of funds
Migration-readyA more than 4K-member Facebook group serves as a natural seed cohort. 2,041 users · 200–300 DAU

Why this matters for your community

You keep ownership of the audience and data. You set the rules. Your members get a fast, familiar experience with stronger safety and a roadmap that serves your brand, not an algorithm.

Get in touch
Intro callBook a 30-min call Emailbusiness@jetruby.com Phone+1-415-906-7704

Thank you for contacting us

Our manager will get back to you shortly. While waiting, you may visit our portfolio.

Check our portfolio

Contact us

By submitting request you agree to our Privacy Policy

By submitting request you agree to our Privacy Policy

Contact us

By submitting request you agree to our Privacy Policy