It looks very helpful! I tried other tools before and the best so far was azure devops - but It's not for PMs. Jira is, well... jira (driven by a pm team that doesn't stop adding useless changes). Trello is just to simple for complex things. I guess upbase is exactly what it needs to have a small and good pm management. I will buy a lifetime license. A question thoug: will it support jottacloud for document storage?…
Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
281–290 of 470 posts
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#282To me personally, your product description here at HN (on top of this page) is more to the point than the copy on the homepage!
To the OP: this is extremely well done. Congrats on launching. Love the design and the packaging.
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#283Does 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.
I just launched the Android app with all networking and mobile disabled, the app showed me all my pages etc and allowed me to enter new data.
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#284To me personally, your product description here at HN (on top of this page) is more to the point than the copy on the homepage!
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#285To me personally, your product description here at HN (on top of this page) is more to the point than the copy on the homepage!
I agree. That should be the "pitch" in the marketing copy. Something like "I got frustrated with Trello, Asana, etc. so I decided to fix it" and build the narrative from there. To the OP: this is extremely well done. Congrats on launching. Love the design and the packaging.
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#286I'm excited to try this. I've done the same dance with PM tools over the years and had similar experiences to OP. I've always ended up back on Teamwork which is amazing but they do a hard sell and the price per head is prohibitive for people in my situation (2 person agency, no interest in "10 seat pricing"). Will be good to check it out!
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#287Earlier quoted context omitted.
Thanks so much for your invaluable feedback and suggestions. We're tech guys, not marketers, so we find positioning really challenging at the moment. Thanks again for taking the time to give us some GREAT advice.
as a founder, you are no longer allowed to say "we're tech guys, not marketers" anymore :) this is now your job. hope you take this great advice and stand out. vsri said it faster and better than i could so will just endorse - please dont say what you think you're supposed to say (leads to generic corporate bs) and say what you really think and give examples to "show, don't tell".
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#288Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#289Does 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.
It’s architected in a way that client syncs the data, all the actions happen locally and then delta packets are synced back to the server. This also makes the app really fast because the client doesn’t have to wait for the network to complete the action.
Re: Show HN: I built my own PM tool after trying Trello, Asana, ClickUp, etc.
#290Earlier quoted context omitted.
This is a huge ask, but would you mind elaborating on your workflow a bit? I really struggled with Jira at work, and I _think_ it was for similar reasons that you described. Are you saying that what is a story at work, and captured within a single “unit” within Jira (I don’t want to use “task”, because that’s a separate thing in Jira) is more broad, but you benefit from having that story broken down further, and that…
Yes. Most organizations I've worked in have an OKR, several epics from that OKR, and several stories from each epic. I tend to work on stories all across those epics, but even broken down stories can never be broken down enough for a single programmer. They're still broad because I'll need to gather requirements from external teams, get a permission here, or dive into a deployment workflow there in order to fully clo…
If a story is your smallest unit of work, does one developer own a story? Or are multiple people working on it? Intuitively it feels like if multiple people are working on a single story then it feels like that should (or at least could) be broken down into subtasks (or checklist items, if you didn’t want to create new tickets) that could be split between developers, and keeping that context and discussion within that ticket, I would think, would be helpful for knowledge sharing and drawing from that discussion to feed into your longer term knowledge base docs.
Just food for thought from someone who tool hops way too frequently with poor short term memory .