...but, “Mirroring” information in two places
I’ve enjoyed XMind for quite some time. Developers are very committed to smooth experience. This is apparent in bugs, assuming they exist, being made transparent.
One suggestion from my side, depending on the roadmap, that will help to keep competitive. Moving away from rigid top down structures (not how we think), apps are trying to find UXs that represent many-to-many bottom-up lookups on the back end.
Some do this miserably with “tag only” systems that delude into piles of information. Others are trying to put the user closer to the database with wikis and record linking features. There is somewhere in the middle, and I think Workflowy just got close.
They’ve implemented what are called “mirrors”, where an instance of information in one bullet can be copied to another bullet half way across the list. The interesting thing is, they’re linked, meaning a change happens in one place reflects in another.
Anyone working with DBMSs knows this is pretty simple on the backend. However, this paradigm shift from folder systems isn’t so simple to the consumer. Mirroring is an analogy that makes sense, is simple, yet very powerful. Unfortunately for Workflowy, despite mastering the list UX, don’t have the mind map.
I’d encourage XMind to find an analogy that makes sense to the consumer to “reflect” the same information’s updates in two different places on a mind map.