301–310 of 470 posts
This is really nice. What is the tech stack? One quick thing i noticed, When i enter new section name and press tab, it is ignored unlike if you press enter, at least in board view. I'd imagine pressing tab after input is typical user behaviour.
I got your point on section naming behavior. We'll optimize it in the upcoming days.
Found a typo on the landing page: "No more switching back and forth between a dozens of apps." Either drop the 'a' or put 'a dozen apps.'
As someone whose team just got bitten - again - by Jira descriptions being overwritten by an unwitting user with unsaved changes, I feel you. I just can’t imagine why it isn’t easy to recover a previous description and its formatting. Jira solves the larger collaboration problems, but blows it on the small stuff. I spent the next hour fuming and imagining how it would work if it was done right (i.e. the way I thought…
https://www.tutorialspoint.com/jira/jira_view_change_history...
Is it possible to create links between documents? It doesn't seem to be a slash command or markdown syntax.
To me personally, your product description here at HN (on top of this page) is more to the point than the copy on the homepage!
Have you looked at Sunsama? I have few ideas on how you can improve this with lots of integrations. I can be reached at fameoflight@gmail.com if you want to chat.
Found a typo on your website on the ClickUp competitive page. “Upbase have global chat. ClickUp doesn’t” should be “Upbase has global chat…”
Does it have offline support? This is the one thing I'm missing the most about Notion, Miro, Google Calendar, and all of this - offline support. In German trains, I'm offline, on flights, I'm often offline; while traveling, I'm often offline. Offline capabilities are often neglected.
Offline support is costly, and we do not have the resources for it yet. For businesses that have a lot of small customers, offline support is challenging.
The storage itself is trivial but for everything else (queries, syncing, conflicts, validation, permissions, schema changes) there's little support and I had to make my own stuff. It works for me, because because I only have 2-3 entities but your app is much more complex, so I wouldn't recommend it even if you started from scratch.
I will say that there's nothing that really stops offline aside from ecosystem support and maturity. All it really takes is a medium-big well maintained project that solves 80-90% of use cases. I think CRDTs are promising for the data layer because it simplifies the API surface (at the expense of complex implementation).
Per user per month = no thanks.
If there is 1 feature that all of these tools neglected, it's speed. They are way too slow loading huge Javascript libraries unnecessarily. By the way, what you are building looked almost exactly like Wrike.
If you test it out for some time, you'll see that it's much different from Wrike.