We found that we were often essentially making lists inside of top-level boxes.
With Miro you basically just get bulleted text lists, which is fine but only gets you so far.
With Plectica you can nest cards inside of cards, which means you can drag drop to re-order, give nested cards their own tags, etc.
So for things like modeling a db schema (lists of columns in tables, each column with its own attributes) or planning user stories (lists of tasks to support use cases, each task with its own parameters etc), Plectica is just really flexible / extensible.
montroser|5 years ago
With Miro you basically just get bulleted text lists, which is fine but only gets you so far.
With Plectica you can nest cards inside of cards, which means you can drag drop to re-order, give nested cards their own tags, etc.
So for things like modeling a db schema (lists of columns in tables, each column with its own attributes) or planning user stories (lists of tasks to support use cases, each task with its own parameters etc), Plectica is just really flexible / extensible.