What does the DNE do?

Tons. The most important function is to organize knowledge visually, in maps where anything can be linked to anything else. But it also does a lot more. Take a look at this functionality list.

Who would benefit from using it?

Anyone who works with information on a computer. Business people, researchers, students and teachers, etc.

Why is it 3D? What's with all the graphics?

We think the graphics are cool. But they are also functional. The DNE is all about managing knowledge visually, in an object-oriented work space. So we take the visuals seriously, and make our objects look like real objects. We probably didn't have to set it in the Pacific Northwest, looking over the ocean, but hey, it's a nice view.

The interface doesn't look like “normal” software. Is it easy to use?

The DNE represents a pretty radical break with what we've seen before. That means that you can't really use it out of the box. But, there is a ton of help materials, and really not that much to learn. It's a visual interface where pretty much everything is right in front of you. In the long run this makes things easier, because you never have to remember commands that are hidden 5 menus deep. But in the short run it does mean that there's a learning curve, and that you will have to spend some time watching our videos and doing the tutorial. Sorry, but it's not possible to be both genuinely “cutting edge” and still work just like everything else.

Why “kNowledge Elements” and “Tiles”? Why not just call them folders and files?

Because NEs and tiles are way, way more robust than folders and files. NEs support many-to-many relations (any NE can be linked to any other NE), and they can be used in multiple models reflecting multiple different contexts. NEs and tiles can be given a wide variety of user-determined meta-data. Many tiles access a file, but a tile isn't always a file: tiles can access subdocuments within files, configurations of other tiles and NEs, web pages, or any other piece of information your computer can access.

How are “fields” different from ordinary file properties?

Fields are up-front and easy to access, completely user-determined, and can be created on the fly. That means that fields can be used to create working software on the fly, without extensive programming experience.

What's the deal with subdocuments? Can't I just use bookmarks?

Unlike a regular bookmark, a subdocument is a bonafide piece of information. It exists in your database, so it's searchable. It can be given independent meta-data fields, can be located anywhere in your DNE regardless of where the source tile is, and can be emailed or included in a map. At the same time, it is not an independent file, so you don't have to maintain multiple files.

Can I try it for free?

Of course. Try it for a month, see what you think.