Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

I Built a Small Scheduling App. Somehow People Found It.

A few weeks ago, I launched a little side project called DaysWeCan. It's a simple tool for finding a day when a group of friends can meet up. You create a group, share a link, and everyone marks the days they're availab

A few weeks ago, I launched a little side project called DaysWeCan.

It's a simple tool for finding a day when a group of friends can meet up. You create a group, share a link, and everyone marks the days they're available. That's pretty much it.

No accounts, no emails, no sign-ups.

I built it mostly because I enjoy working on small projects, and coordinating plans with friends is one of those things that always seems more annoying than it should be.

After launching it, I added a few SEO pages, submitted the site to Google, and moved on to other things.

I didn't post about it anywhere. I didn't send it to friends or family. I hadn't really done anything to promote it.

So I was a little surprised when I checked the data a few weeks later.

People were actually using it.

Five groups I didn't create

When I looked at the data, I found five groups that weren't mine.

That might not sound like much, but considering I hadn't told anyone about the site, I thought it was pretty cool.

Two groups stood out. One had eight members, and another had five.

At first, I figured people might just be creating groups to try things out. But when I looked at the availability data, it seemed like they were actually trying to plan something.

Here's what I found:

Metric Result
Groups created 5
Total group memberships 16
Saved availability marks 119
Groups with multiple members 2
Groups with saved availability 3

The five-member group had 85 availability marks, with every member having marked at least one day.

In the eight-member group, six people had added their availability.

I know these numbers are tiny. But seeing an actual group of people use something I built felt a lot more meaningful than seeing a bunch of page views.

Someone had found the site, created a group, shared the link, and gotten other people to participate.

I thought that was pretty neat.

Where did they come from?

My first guess was Google.

I'd added some basic SEO pages when I launched, and Google Search Console showed 188 impressions and six clicks over the first few weeks.

A few of those clicks happened around the same time the groups were created.

That doesn't prove anything, though. I haven't set up proper attribution, so I don't actually know where those users came from.

But it got me thinking about something I hadn't really considered when building the app.

Unlike a normal website, where every visitor needs to find it on their own, a tool like this only needs one person to discover it.

That person creates a group and shares the link with five or eight friends. Those friends then get introduced to the tool without ever searching for it.

Of course, that doesn't mean they'll come back or create their own groups. But it's an interesting aspect of this kind of product, and something I'd like to keep an eye on.

One thing I didn't expect

While looking through the data, I also checked how many groups had found a date when everyone was available.

The answer was zero.

Not a single group had a day that worked for all its members.

The five-member group came close, with four people available on the same date. The eight-member group had a date that worked for five people.

I found that pretty interesting.

People were clearly interacting with the calendar, but I couldn't tell whether they'd actually managed to make plans.

Maybe they went with a date that worked for most people. Maybe they discussed it in a group chat afterward. Or maybe they gave up.

There's no way for me to know right now.

It's made me realize that tracking activity is one thing, but figuring out whether people actually got what they came for is a different problem.

A bit about how it's built

For anyone interested in the technical side, the stack is pretty small:

  • React and TypeScript for the frontend
  • Cloudflare Workers for the backend
  • Cloudflare Durable Objects with SQLite for storage
  • WebSockets for real-time updates

Each group gets its own Durable Object, which manages members and their availability.

I wanted to keep the infrastructure simple, so there's no separate database server or authentication system to deal with.

One design decision I made early on was to make groups reusable.

Most scheduling tools focus on creating a poll for a specific event. With DaysWeCan, the idea is that you can keep the same group of friends and just update your availability whenever you want to plan something.

Whether people actually use it that way remains to be seen.

What's next?

I'm trying to resist the temptation to add more features.

It's easy to think of things that could be useful: reminders, notifications, calendar integrations, and so on.

But right now I'm more curious about whether people will continue using the app as it is.

A few things I want to find out:

  • Will more groups appear without me promoting the site?
  • Will people come back to existing groups?
  • Are groups actually managing to agree on dates?

I might add some lightweight analytics to better understand what's happening, but I don't want to overcomplicate things just yet.

This is still a very small experiment. Five groups aren't enough to draw any serious conclusions, and I have no idea whether anyone will still be using the app a month from now.

But I do like the fact that a few strangers somehow found a little tool I built and decided to use it with their friends.

That's a pretty nice feeling.

If you want to check it out, it's at dayswecan.com.

Tags: #webdev #cloudflare #buildinpublic #sideprojects

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.