760 karma · joined October 20, 2015
I had personally not used stores a lot before, but realized how powerful they were in the project. I would try to abstract away as much as possible of the Firebase stuff and having your components talk to the store as data source. This makes it a lot easier for real-time stuff to work right (but also auth, you want to make sure to update state across the page once users log in or out).
I hope for Calenday to implement features specifically for trip planning (although I am also trying to find other applications). Ideas I were considering are adding location-aware functionality like figuring out travel time and such.
I really appreciate your comment about finding a niche and fixing pain points there. Certainly a less clear path, but more fruitful too as you mentioned.
Good points, thank you for taking the time to put this together!
I should surface this better, but you can click and drag on the calendar or drag the event button to the calendar to quick add!
Writing is more challenging, I haven't found a nice solution so I resort to making calls with the Firebase SDK directly (but those updates are then surfaced nicely again through the store).
I am not sure on how to best indicate it, but it might be interesting to show availability of each person as a shaded background. Darker shade would mean more people present. I will put it on my backlog, thank you!
Do you have any in mind? Definitely interested to hear of any ideas!
I built this website after having to recreate the same Google Sheets template over and over for different trips. This is basically Google Docs for calendars along with some other helpful features like voting and categories for trip ideas.
The website itself was built using SvelteKit with Firebase for the database and authentication, all hosted on Vercel.
Feel free to ask anything!
I think for my use case specifically, the library was kind of overkill though and something like librosa [2] would have been enough for feature extraction.
> Special characters \, ;, ,, " and : should be escaped with a backslash (\) as in MECARD encoding.