4 ms·

Perhaps instead of new tools to compete with the entrenched, we should be building new frontends. How many people forced to use JIRA or Salesforce would jump a

• solatic 2y ago
  A different frontend wouldn't fix Jira. It's slow because the underlying APIs are slow. The frustrations mount mostly from the sheer number of rules that are built on top of it by users; if your alternate UI obeys those rules it will still frustrate users.
• jitl 2y ago
  (I work on a tool completing with the entrenched) Building one’s business solely dependent on the grace of another’s API access is a pretty precarious position. Beyond that the incumbent APIs are usually slow and severely rate limited. Building improvements on top would necessitate a complex sync/caching system, plus if you want to layer on real time collaboration your job is even harder since you need to maintain your own state (for collab in your CRDT format or whatever) that you periodically reconcile with the underlying tool. At that point, you already need a complete backend so you might as well be a stand alone product and just offer 2-way sync with the incumbent as a value add feature. Anyways, we built something like that https://www.notion.so/help/guides/synced-databases-bridge-different-tools https://www.notion.so/help/guides/synced-databases-bridge-di...