tomosterlund

A bit early to migrate a UI library to Temporal?... Not really!

1) SEO texts. Try phrasing like "alternative to {competitor}" for free-riding off your competitors back.

2) Get backlinks. Make sure other websites have links to yours. This will increase your ranking in search machines.

3) Do social media

surprises me a bit about increasing speed.

I would have thought that people who constantly rush it when walking suffer more from stress.

But then maybe the study was more focused on people who did walking as a sort of sport activity than a way of just getting outside?

Very cool app! Are you considering adding a self-hosting alternative?

Idea: you could for example do something like a €199 one time fee for people who'd like to self-host.

I think this is something a fair bit of small SaaS founders need, but tbh I don't think this is one of the most crucial things to have a subscription for.

Amazing! This is so helpful for anyone building open source, wanting to avoid committing with the work email by mistake.

Thanks

I think this is a beautifully written article. There might be a lot of gems to learn from here. One thing makes me a bit sceptic though:

"Clear your schedule, and read this book"

I haven't been around many years in the private sector, and haven't sold much. But I sometimes have a feeling, many project-strategies are kind of over-engineered and so meticulously thought through, that no actual work happens. This seems like an anti-pattern for achieving things to me.

"Third, talk to a lot of people" however really resonates with me, because if there is one thing I see all the time with successful new products in my field, is that they have built very strong communication channels with users and people interested in the product.

Amazingly pretty! I'm not international enough to have a personal use case for this, but I admire the skill that went into this. Are you open sourcing this at some point?

Thank you so much! It sure did, and still does teach me a lot

You're right, the demo does not show it yet. Perhaps I should change that. However, in the demo you could drag one event onto another, and then you'll see how it looks when it's overlapping with another one.

Thank you so much for these kind words :)

This is gold for me. Thank you so much for taking the time!

Will be sure to actually do a word-by-word reading of the spec before taking on recurrence x)

Correct! In the week- and day views there is still no gap, only in the month view. The discussions here today though convinced me I should also allow for a gap in the week/day views (not sure yet if per default or configuration).

Thanks!

Do you mean if any existing calendar can be used a backend? In that case, not out of the box. But I do intend to build a plugin for using Google Calendar as a backend.

Thanks! I appreciate it :)

Resizing is one of the next tasks in my backlog.

Ah of course! Thanks a lot

Thanks! This is a great question.

I intend to implement event recurrence, but this is definitely one of those things which will require changes across most packages of the project code. The details of how it will be implemented is still open :) Will surely look to other open source calendars for inspiration. Do you have any tips on solutions/APIs you like?

I respect your opinion, but I strongly disagree :) Fullcalendar is a great calendar, but it is not material design.

I like it! Never thought of this. Probably I could solve this by allowing an implementer to configure a range of days to be shown for each week.

Thank you so much! I really enjoy it as well. I build them privately since 2 years, and at work too. For some reason I'm also still having a great time doing so.

Thanks for sharing. Will look into Kiko! Though my main focus for now is to build the best possible open source calendar, I'm also pondering on ideas for possible business models to accompany it later on.

Thank you so much :)

And about the gotchas: Yea, I feel ya! This is my third stab at building a regular event calendar. At work I also build scheduling tools. Still, I discover these gotchas anew on a regular basis.

Most important learning so far, which also costed me the most before I knew it, was to always run my CI-pipelines in different time zones.

This would be one way. Another way, which fullcalendar does, and which I intend to implement down the road, is Google calendar. You can actually use their calendar as a backend, and fetch the events from it to display elsewhere.

"Hey" there ^^ Thanks a lot, I neither knew Hey nor their new calendar. I'll be sure to check it out tonight.

This makes perfect sense! I'll put this into the project roadmap, to leave a few pixels for clicking next to events on also in the week grid.

Simple answer: I never thought of it.

But when I think about it, it absolutely makes sense. I'll definitely consider if this should be the default behavior of the month grid in v2.

Thanks a lot for your input!

Cool! I like the idea. This would also be possible to implement as a custom view in Schedule-X. If you want I can bump this thread once I've documented how to build a custom view? Or you could also join the Discord chat where I'll try and post new feature releases.

This is a good point. The Google calendar actually has a gap in the week view too. I just didn't understand why. Do you think it would look better if the gap exists in the week view as well?

Hi, thanks for dropping this feedback.

Yes, as of now, the demo does not utilize the APIs for adding, editing or removing events. But this definitely helps me understand that it might make sense to do so! I'll put this in the project backlog; the APIs exist, the demo just doesn't use them.

Hi. Thanks a lot :)

There is a dedicated React component for this: https://schedule-x.dev/docs/calendar/react

This is a good question, which baffled me a bit too when studying the Google calendar.

Took me a while to figure it out, but when I first built the month grid without subtracting a few pixels per event, it got a bit hard to optically make sense of where an event ended and a new one started. This especially since events are also allowed to stretch over multiple days.

Subtracting a few pixels from each event, helps me to quicker grasp that an event ends on a given date, and isn't to be considered "one" with an event in the next day.