0%
WeAmor
WeAmor

Case Study

WeAmor

A cross-platform dating app that replaces the mutual-match wait with a credit-powered direct request, so a conversation can start the moment a user wants it to, not whenever the algorithm allows.

Industry
Dating & Social Networking
Solution Type
Cross-Platform Dating App
Duration
8-9 Months
Services
Mobile App

Project Summary

WeAmor approached Tibicle to build a dating app around a single conviction: that the best part of a dating app shouldn't be locked behind a mutual swipe. Before WeAmor, the founding team had a clear product thesis but no working way to express it. Conventional dating apps make users like, wait, and hope, a flow that leaves most conversations unstarted and most users unsure whether anything is happening at all. WeAmor's answer was a credit system: buy credits, send a direct request, start talking. Simple as a concept, but it meant two fundamentally different interaction models free social gestures and paid direct access had to live side by side in one interface without confusing users or quietly spending their money. Tibicle designed and developed WeAmor end to end: a Flutter application shipping to both the App Store and Google Play from a single codebase, Firebase handling authentication, profiles, media and push, and Socket.io powering the real-time messaging layer that makes "no waiting" literal rather than aspirational.
Project Summary

The Challenges

Making Paid Access and Free Interaction Coexist in One Interface

A dating app that charges for access has to be unmistakably clear about what costs money and what doesn't. Early in the build, the free and paid interaction paths were surfacing together in the same part of the interface, and the ambiguity undermined the entire premise, alongside the technical demands of real-time chat, two-store billing, and discovery that had to feel immediate from day one.

Like and Paid Actions Colliding in the Same Interface

Free likes and paid direct requests shared the same action area, causing confusion, accidental taps, and unintended credit usage.

No Way to Signal Serious Intent

Users had no way to distinguish genuine interest from casual swiping, making meaningful requests difficult to communicate.

Real-Time Messaging That Had to Feel Instant

The app needed fast, reliable messaging with real-time delivery, presence, typing, and delivery status.

Two Billing Systems, One Wallet

Credit packs and subscriptions had to stay accurate across both App Store and Google Play.

Discovery That Had to Be Relevant From Day One

The app needed to surface relevant, trustworthy matches using interests and location from the start.

One Product, Two App Stores, One Team

iOS and Android needed a consistent experience and synchronized releases without separate native teams.

Our Solution

Tibicle built WeAmor as a complete cross-platform dating product, rebuilding the interaction model from the backend up so that free and paid actions could never be mistaken for one another, and wiring a real-time layer underneath so the promise in the name held.
Instant Direct Requests, Powered by Credits

Instant Direct Requests, Powered by Credits

The feature the whole product is built around. Instead of liking and waiting, a user spends a credit and sends a message request directly to the person they want to talk to. Because a credit has real cost, the request carries information the recipient can read: this person meant it. Packs are sized to actual usage rather than arbitrary tiers, so the cost of starting a conversation stays legible.

  • Send a direct message request to any profile without waiting for a mutual match
  • Credit packs sized to real usage 1 credit for 3 messages, 5 for 15, 20 for 60
  • Spending a credit signals genuine intent, so a request stands apart from an idle swipe
  • Recipients keep full control  a direct request can be accepted, ignored, or blocked
  • Balance, spend history, and per-action cost visible at all times, never buried in settings
Real-Time Messaging on Socket.io

Real-Time Messaging on Socket.io

Once a request is accepted, the conversation has to feel like a conversation. A persistent socket connection replaced polling entirely, so messages, presence and typing state move in real time and the layer is built for mobile reality, where connections drop in lifts, on trains, and between cells.

  • Persistent socket connection for instant delivery no polling, no pull-to-refresh
  • Live typing indicators, read receipts, and online presence
  • Message queuing and automatic reconnection, so nothing is lost on a dropped connection
  • Firebase Cloud Messaging push for conversations that arrive while the app is closed
  • Per-message delivery state, so users always know whether something landed
A Unified Credits & Membership Engine

A Unified Credits & Membership Engine

Two stores, two purchase types, one wallet. Consumable credit packs and recurring memberships were built on a single entitlement engine with server-side receipt validation, so the user's balance is the same number whether they signed in on an iPhone or an Android device and renewals, expiries and failures resolve without anyone at WeAmor touching them.

  • One wallet behind both consumable credit packs and recurring memberships
  • Server-side receipt validation for the App Store and Google Play
  • Membership tiers at 1, 6, and 12 months, with entitlements applied the moment a purchase clears
  • Automatic handling of renewals, expiries, refunds, and failed payments
  • Identical balance and entitlement state across iOS and Android
  • Purchase and spend history the user can audit themselves
Smart, Inclusive Discovery

Smart, Inclusive Discovery

Discovery was built to work from a standing start. Rather than waiting on months of behavioural data, matching weights shared interests, location proximity and recent activity — with preferences the user sets explicitly rather than ones the system infers. Verification and moderation run underneath it, because a direct-request model only works if the profiles on the other side are real.

  • Matching weighted on shared interests, location proximity, and recent activity
  • Open to all genders and orientations, with preferences the user states rather than the system guesses
  • Profile verification and photo moderation to keep the pool credible
  • Report and block available from every profile and every conversation
  • Tuned to return relevant results on day one, not after months of training data

How We Deliver

Bringing WeAmor to life meant turning a founder's thesis, that nobody should have to wait to start a conversation, into a working product shipping on two app stores. Here's how we structured that journey from first requirement to final release.
How We Deliver
Our development process for WeAmor was structured to keep pace with the project's scope, from Requirements Analysis through Delivery and Release, while working closely with the client to meet the 8-9 month timeline. Every stage, from Wireframe Design to End-to-End Testing, was tailored to build an interaction model where free and paid actions stay unmistakably distinct, and a real-time layer that makes instant messaging genuinely instant. App Store and Play Store submission, review, and in-app purchase compliance were handled as part of delivery. Even after launch, our Support & Maintenance services continue to ensure WeAmor runs reliably as the user base grows.

Outcomes Delivered

Since launching on the App Store and Google Play, WeAmor has put instant connection in users' hands, with the interaction model rebuilt so that every paid action is deliberate and every free one is unmistakably free.

50K+

Downloads Across Both Stores

Live on Google Play and the App Store from a single Flutter codebase.

3×

More Conversations Started

Direct requests opened conversations a match-gated flow would never have produced.

90%

Drop in Accidental Credit Spend

Separating free and paid actions in the backend and UI removed the mis-tap problem.

2

Platforms, One Codebase

iOS and Android shipped and maintained in parity, without a second native team.

Tech Stack

WeAmor is built on Flutter, shipping a single codebase to both the App Store and Google Play without compromising the feel of either platform. Firebase handles authentication, profile data, media storage and push notifications, while Socket.io powers the real-time messaging layer that keeps delivery, presence and typing state instant the technical foundation the "no waiting" promise depends on.

Got an Idea?
Get FREE Consultation

In our world, there's no such thing as having too many clients

icon
Phone
+91 9724922880