Built Dapp — a Hyperlocal Closed-Community Dating App

Hyperlocal Closed Community App

While I was pursuing my bachelor's degree, I built Dapp, a hyperlocal closed community app aimed at helping people meet, chat, date, organise small events, and socialise within a familiar setting.

Instead of creating an open platform,

Dapp was intentionally designed as a closed community.

Only students from a single college could sign up. This helped create trust, kept interactions relevant, and made conversations feel more natural.

What the Dapp offered

Dapp combined a few simple social experiences into one place:

• Dating and networking — a swipe-based discovery flow that helped students find and connect with others on campus.
• Instant events — a live updates section where users could share what they were doing and invite others to join in real time.
• Gossips forum — an anonymous, Reddit-style space for campus conversations, opinions, and everyday chatter.

The app was built entirely using GlideApps, a no-code platform. This made it possible to design, launch, and iterate quickly without a full engineering setup.

Launch and early traction

Dapp was launched within my college as a controlled beta.

• Access was limited to verified students
• A joining fee ranging between 49–99 was introduced to keep participation intentional (we were not sure about how to price it right)
• We were able to bring in 100+ paid users in the first month (we had to close by the second month sadly)

Engagement picked up faster than expected. Swipes, chats, and forum activity grew steadily, and it became clear that people were actually using the app, not just installing it out of curiosity.

The reality check

As usage grew, so did the amount of data being generated. Swipe activity and chat records started increasing quickly, and on GlideApps, that directly meant higher operating costs.

That's when it became clear the app hadn't been planned for scale. Without the budget to support the rising infrastructure costs, I decided to pause the app rather than force it to continue.

What I realised is that:

• Closed communities tend to drive stronger engagement than open platforms
• No-code tools are great for testing ideas, but they have real scale limits
• Early traction only matters if the system can support growth
• Building something quickly is one thing, sustaining it is another

Dapp was paused not because the idea failed, but because it grew faster than the system it was built on. The project gave me hands-on experience in product thinking, user behaviour, monetisation, and the real challenges of scaling even a small platform.