When I first joined this platform, I instantly loved the premise. A clean writing experience with some great discussions, no frills, a focus on content rather than people, and no unnecessary clutter. But I also noticed a lot of room for improvement, which I shared just 10 days after joining the platform. It's been 8 months since then, and I have some more ideas that I think could make Cake an even better experience for all of us.
Remember back in the old days of internet forums, where a thread would be created, then other threads would be created, so the first thread would get pushed down the list, but then someone would post in the first thread, and it would go back to the top of the list again? I think Cake could potentially benefit from something like that, but not exactly like that. Case in point, this conversation about Google Stadia by @jpop that was written back in March. Google recently announced pricing and availability, and @Victoria reignited the conversation by updating it with this new info. So now people who are already following the conversation will get a notification about her post, but people who missed the conversation a few months who might also be interested in the topic will now be left out. This kind of scenario could benefit from a "bump" back to the top of people's home feeds, but at the same time I know it wouldn't be feasible to bump every single conversation that receives a new post. Maybe someone else could come up with a more elegant solution?
Recommend for Featured
@apm suggested this a few months ago and I think it's a great idea. Assuming the selection of Featured posts is a manual process, and assuming Cake will continue to grow in both membership and content, I feel like the team might eventually be unable to cope with the number of conversations posted daily, which could lead to some gems being missed. A simple button for readers to recommend a post might do the trick, highlighting potential Featured posts for the team to evaluate, or maybe something like a reaction/reply counter, so when a post generates enough interaction it could be highlighted for the team to take a look? Something like that.
Sometimes I struggle to visually identify new notifications because they just blend with old notifications. There's no divider between new and old notifications, and the blue hue for new notifications is so subtle I sometimes have difficulty differentiating them from old notifications. So maybe a more apparent design element to better differentiate between old and new notifications? I'd also like to suggest that notifications from the same conversation are marked as read once the conversation is viewed. As it stands, I could get three notifications from one conversation, click on one to view the conversation, go back to my notifications, and the remaining two notifications from the same conversation would still be "new" when they should already be "read". Lastly, linking back to my previous section, it would be nice to be notified when a conversation of ours is featured, since the only way to know if it was featured would be to view the post manually.
Lastly I just want to resurface some of my old suggestions from my previous post in hopes that they may be revisited by the team again, such as a proper draft system which allows us to draft multiple posts with multi-device access, an Android app (or at least better support in mobile browsers), and integration with Google Photos.
Hope @Chris and his team continue to make Cake better! I really enjoy this network and want it to thrive.