CoffeeChat

CoffeeChat

Role

Proposal and scope

Team

Dev team

Platform

Mobile PWA

Timeline

5 weeks

project overview

Attendees at a big convention want to network, but starting a conversation with a stranger is awkward. The client wanted an app to make that easier: find someone, say hello, agree on a time, and meet over coffee.

Attendees at a big convention want to network, but starting a conversation with a stranger is awkward. The client wanted an app to make that easier: find someone, say hello, agree on a time, and meet over coffee.

TL;DR

  • The client wanted an app that helps convention attendees meet and talk to each other.

  • They came in expecting native Android and iOS apps.

  • With a fixed event date, I recommended a web app that installs from the browser instead, and the client agreed.

  • The app was delivered and used at the event. I have no usage numbers, so this is a scoping story, not a results story.

The key decision: native apps vs. a web app

The client's first plan was two native apps, one for Android and one for iOS. Building them was possible. Getting them live was the problem: app store review and approval is outside our control, and the deadline was fixed. An app that exists but can't be downloaded before the event helps no one.

I recommended a web app that attendees open from a link and add to their phone's home screen. It looks and feels like an app, works on both Android and iOS, and needs no store approval. I explained the trade-off in plain terms, and we agreed on it together.

What went into the first version

Each feature answers one question an attendee would have:

  • Sign in with Google, Apple or email: how do I get in without friction?

  • Profiles with work background, interests and coffee preference: what can I talk about with this person?

  • A map of approved cafes and who's available: where do we meet, and who's around?

  • An icebreaker assistant, "Brewie": what do I say first?

  • In-app chat: how do we agree on a time?

  • An admin dashboard: how does the client manage the cafe list and see activity?

Keeping the project unblocked

Maps, sign-in, chat and the AI assistant all depend on outside services. I listed in the proposal what the client had to provide up front: their own accounts for those services, the list of cafes and the event schedule, and final brand assets. With a tight deadline, waiting on any of these would have cost days we didn't have.

Result

Delivered on time for the event and used by attendees. I won't claim numbers I don't have.

TL;DR

  • The client wanted an app that helps convention attendees meet and talk to each other.

  • They came in expecting native Android and iOS apps.

  • With a fixed event date, I recommended a web app that installs from the browser instead, and the client agreed.

  • The app was delivered and used at the event. I have no usage numbers, so this is a scoping story, not a results story.

The key decision: native apps vs. a web app

The client's first plan was two native apps, one for Android and one for iOS. Building them was possible. Getting them live was the problem: app store review and approval is outside our control, and the deadline was fixed. An app that exists but can't be downloaded before the event helps no one.

I recommended a web app that attendees open from a link and add to their phone's home screen. It looks and feels like an app, works on both Android and iOS, and needs no store approval. I explained the trade-off in plain terms, and we agreed on it together.

What went into the first version

Each feature answers one question an attendee would have:

  • Sign in with Google, Apple or email: how do I get in without friction?

  • Profiles with work background, interests and coffee preference: what can I talk about with this person?

  • A map of approved cafes and who's available: where do we meet, and who's around?

  • An icebreaker assistant, "Brewie": what do I say first?

  • In-app chat: how do we agree on a time?

  • An admin dashboard: how does the client manage the cafe list and see activity?

Keeping the project unblocked

Maps, sign-in, chat and the AI assistant all depend on outside services. I listed in the proposal what the client had to provide up front: their own accounts for those services, the list of cafes and the event schedule, and final brand assets. With a tight deadline, waiting on any of these would have cost days we didn't have.

Result

Delivered on time for the event and used by attendees. I won't claim numbers I don't have.

Other Projects

Other Projects

Other Projects