{"id":32606,"date":"2024-12-14T10:51:12","date_gmt":"2024-12-14T18:51:12","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=32606"},"modified":"2024-12-14T10:51:12","modified_gmt":"2024-12-14T18:51:12","slug":"mindnode-next","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2024\/12\/mindnode-next\/","title":{"rendered":"MindNode \u2192 MindNode Classic \u2192 MindNode Next"},"content":{"rendered":"

When the developer of iThoughts decided to shutter the doors on his business, I chose MindNode as my new mind mapping tool of choice. My post in April entitled RIP iThoughts<\/a> is probably in my top ten most-commented articles. Many people jumped into the discussion just to say thanks for the trade study while others joined in to offer alternative solutions. It\u2019s been great having a group of people to share a common topic of interest.<\/p>\n

Just 9 months later and big changes are coming to MindNode. I\u2019m not ready to call the changes a success but I\u2019m really intrigued by the path the company has taken. Imagine you rewrite your flagship product from the ground up and it\u2019s working great, but it\u2019s not yet in feature parity with the previous version? You have a couple of choices.<\/p>\n

One path would be to sit tight and keep working your little coding fingers to the bone until 100% of the features in the old product are available in the new. Or, you could go down a risky path where you release the new version (missing some features) and have it exist almost side-by-side with the original.<\/p>\n

That second path is what the folks at MindNode have chosen to do. I think it\u2019s a path with a lot of merit, but it could cause people who don\u2019t understand what\u2019s going on to abandon the new software or leave bad reviews for it. My goal is to explain what they\u2019re doing and then with knowledge, you can decide if you think they\u2019re on the right path.<\/p>\n

Naming Convention and Availability<\/h2>\n

First, let\u2019s understand the naming convention. The original MindNode has been rebranded as MindNode Classic, and the new hotness is called MindNode Next. I think it will be pretty easy to keep those names straight.<\/p>\n

For the time being, the only version you can get through Setapp is MindNode Classic. They believe they\u2019ll probably replace it with MindNode Next eventually, but they have to figure out how to make that transition.<\/p>\n

\"MindNode
Only MindNode Classic is in Setapp<\/figcaption><\/figure>\n

In the iOS App Store and the Mac App Store, the only option you’ll see is MindNode Next.<\/p>\n

\"MindNode
Only MindNode Next is Listed in the Mac App Store<\/figcaption><\/figure>\n

But don’t panic. It’s not gone, it’s just unlisted. At mindnode.com\/article\/mindnode-classic<\/a> you’ll find direct links to MindNode Classic in both the Mac App Store and the iOS App Store.<\/p>\n

\"MindNode
MindNode Classic is Unlisted in the Mac App Store but it’s Still There<\/figcaption><\/figure>\n

Here\u2019s an even more interesting tidbit \u2014 they\u2019re still developing MindNode Classic and adding features. I\u2019m sure new development will slow down as the two versions converge, but it gives me a good feeling about their dedication to a smooth transition. You can run both apps side by side right now and for the foreseeable future. I\u2019m sure they\u2019ll sunset MindNode Classic at some point but it won\u2019t be anytime soon.<\/p>\n

If you want to keep up to date on the development of both products, you can go to mindnode.com\/releases<\/a>. When you look at the release page, you need a magic decoder ring (which I\u2019ve suggested they should include on the page). If you see a feature that says 2024.x, that means it\u2019s a feature added to MindNode Next, and if one says 2023.x, it\u2019s for MindNode Classic. I’ve been surprised at how often I see updates on this release notes page.<\/p>\n

One more naming convention. You can use MindNode Classic and MindNode Next without paying a single hooneyakker. You get a limited feature set but it might be everything you need. If you want the full feature set, you can subscribe to MindNode Plus (for both versions) for $25\/year or $3\/month. If you want to compare features between free and Plus, check out mindnode.com\/download<\/a>.<\/p>\n

Features of MindNode Next<\/h2>\n

Let\u2019s talk about MindNode Next. I\u2019m not going to give you any kind of a deep dive on the product until I have time to really dig into the app, and I\u2019ll probably wait to do that until it\u2019s more in feature parity with MindNode Classic.<\/p>\n

I keep talking about the lack of features but I haven’t explained what’s missing. The MindNode folks have created a great page where they document (using a mind map) what features are in MindNode Classic, and how they\u2019re progressing on shipping those features: mindnode.com\/article\/features-classic-next<\/a>. Let’s talk about some of the new features and talk about what’s missing.<\/p>\n

Document Management<\/h3>\n

One of the biggest changes in MindNode Next is that it is no longer document-based, rather your documents are managed directly in the app and stored in iCloud. If you feel strongly about the ability to see your documents in Finder, then this won\u2019t be a welcome change. The main reason I care about an app being document-based is to ensure portability. If the import and export options are solid, I think I can live with it.<\/p>\n

I can say that in my limited first use of the app, iCloud syncing works really well. Changes on one device were visible nearly instantaneously on my other devices. With iThoughts being document-based, I was constantly finding \u201cconflicted\u201d versions of a mind map with no way to tell which one was the right one, so maybe this is a good change.<\/p>\n

Import\/Export<\/h3>\n

In the currently shipping version of MindNode Next, you can only import MindNode Classic files, plain text files, and Markdown files. On the \u201cplanned\u201d section of their roadmap, you will be able to import OPML, RTF, TextBundle\/TextPack, FreeMind, SMind, MindJet MindManager, and \u2026 my beloved iThoughts. I breathed a sigh of relief when I read that as import of iThoughts was one of my top criteria.<\/p>\n

Remember how I said I thought it was risky to come out with the new app when it wasn\u2019t quite baked? I suspect many people will declare MindNode Next \u201chot garbage\u201d due to its limited file format import capabilities. I’m specifically trying to calm people down because I panicked when I saw it couldn’t import iThoughts and immediately posted that I was looking for a new mind-mapping application. Don’t be like me, give them a minute to get more features implemented.<\/p>\n

I said you can import plain text, Markdown, and MindNode Classic files, but you’ll likely be baffled as to how to accomplish that feat. You won’t find File \u2192 Open or Import option in the menu bar. I wrote to my contact at MindNode, and they explained you have to start from the Finder. Select a file you want to import, right-click, select Open With, and choose MindNode Next. You could also drag the file onto the MindNode Next icon in the Dock. I suggested that perhaps a little hint about that in the app might reduce confusion and keep a few haters calmed down.<\/p>\n

Export is a lot easier – there\u2019s an obvious sharrow where you can export to a MindNode Classic file, PDF, SVG, Image, Markdown, or text. SVG stands for Scalable Vector Graphic, which means these images can be resized without losing any quality, so that\u2019s super cool for a mind map, especially a giant complex one like my iOS 11 Settings Mind Map of Doom<\/a>.<\/p>\n

Collaboration<\/h3>\n

One of the biggest new features of MindNode Next is that you can now collaborate with others. I haven\u2019t been able to test this with anyone yet but I\u2019m really looking forward to seeing how that works. I could see it as a great way to brainstorm with someone on a topic since you\u2019re supposed to be able to see changes in real-time.<\/p>\n

Inline Inspector<\/h3>\n

With MindNode Classic, they used a right sidebar to change things like fonts, and the color or shape of a node. You can still do that with MindNode Next, but they also have a new inline inspector that pops up when you select a node. In addition to the styling options, the inline inspector includes a fold button to quickly fold and unfold nodes beneath the currently selected node.<\/p>\n

But Wait, There\u2019s More<\/h3>\n

According to the page where they document new features in each release, they say you can use Apple Image Playground to create images based on your node\u2019s content. They also say you can ask Siri about the content of your document and let Apple Intelligence summarise it. I haven’t figured out how to do any of that just yet but remember this isn’t a review of MindNode Next.<\/p>\n

Bottom Line<\/h2>\n

The bottom line is that I\u2019m going to give the folks at MindNode a chance to succeed with this new version. I’ll wait to judge MindNode Next until it\u2019s at feature parity with MindNode Classic. Over the upcoming months, I\u2019ll be using MindNode Next \u201cin anger\u201d as the Europeans say \u2014 putting it through its paces with my real work with mind maps, so stay tuned for a future review.<\/p>\n

I hope you\u2019ll keep an open mind about MindNode Next and give them some space to make it even better than MindNode Classic.<\/p>\n","protected":false},"excerpt":{"rendered":"

When the developer of iThoughts decided to shutter the doors on his business, I chose MindNode as my new mind mapping tool of choice. My post in April entitled RIP iThoughts is probably in my top ten most-commented articles. Many people jumped into the discussion just to say thanks for the trade study while others […]<\/p>\n","protected":false},"author":1,"featured_media":32610,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[147],"tags":[1829,1828,2695,6840,6839],"class_list":["post-32606","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","tag-ithoughts","tag-mind-mapping","tag-mindnode","tag-mindnode-classic","tag-mindnode-next"],"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2024\/12\/MindNode-logo-1040x520-1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/32606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=32606"}],"version-history":[{"count":4,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/32606\/revisions"}],"predecessor-version":[{"id":32615,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/32606\/revisions\/32615"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/32610"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=32606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=32606"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=32606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}