> I've been working for quite a while on a new issue tracking/project management tool. The goal was to make it as a native cross-platform application (think Sla

> I've been working for quite a while on a new issue tracking/project management tool. The goal was to make it as a native cross-platform application (think Slack), with potential offline support. I don't know that this is a huge benefit in a work tracking tool. These features are useful in Slack because it's a real-time communication platform. Work tracking systems are more ok with being asynchronous - there's usually a business function that performs synchronization whether or not your work tracking system does, so having everything update across multiple cached versions in real-time is less meaningful. I would focus on the process - it sounds like you're just building something to build something. What in the process of software development is broken? Is building a new tool the right solution?