3 reasons why you should consider Klynt as the best tool around (in case you are wondering ;-)


The number of interactive storytelling apps has been growing like crazy since we launched Klynt first public release back in 2009.

If you are considering starting a new project and looking for an app to help you build your interactive project, you may wonder which one to choose.

Of course, some will consider the brand new tool first, some will look at the aesthetics of the interface while others will be interested in productive features and ergonomics. Whatever your inclinations are, here are 3 main criteria which can help you make the right decision and distinguish Klynt clearly from other tools.

#1 The right mix of features



While most of the storytelling apps offer similar features like the ability to weave photos, videos, texts and any web object together, there is always something that will make all the difference for you.

Maybe you believe scrolling and parallax effects are the future of storytelling! In this case, such tools like Scrollkit, Shorthand, Creatavist may be your best bet.

Maybe the only thing you want is to add simple information layer on one video. So look for storygami

Of course, this is about finding the right mix between the diversity of features & the specialization of the tool. With Klynt, our main focus has always been to help our authors freely explore different narrative formats while offering them special features to organize and share their story in a convenient manner. Check-out our brand new smart mindmap widget, search feature and mini-player for example which allows easy integration of your project on any blog. Who knows, they might be already on your top feature wishlist!

#2 Desktop App or Web-based app?

There are a couple of reasons why we wanted to keep Klynt a stable and reliable PC & MAC desktop app just like Photoshop or Final Cut. First, we believe our authors should be able to edit their projects offline if they want to. In the train, in a classroom, in a conference room, in a country retreat… We want you to work fast, as fast as your computer can, not your internet connection!

Last but not least, Desktop apps usually come with a different pricing model than web based apps. At Klynt, we offer a simple license fee where you do not feel trapped into a pay as you go model. Actually, we believe you should be paying less if you use it more. Not the other way around. And this is one of the great advantage of Klynt Desktop App one-time fee licensing compared to web based apps subscription model.

#3 Open source, API?!

You will most certainly enjoy Klynt user-friendly code-free wysiwyg interface, but there may be a time not far from now when you will want to go further and benefit from the talent of this great developer ready to give you a couple of hours to help you fine tune your project. This is where Open Source Lincensing and APIs comes into play and can be supremely useful!

Now, here are the practical questions you may want to ask about using a so-called “Open Source” solution:

- Can I (or someone else) modify the source code ? Whatever trust you have in the team and infrastructure behind your software, you know the life span of everything is limited and failure is human. So let’s say a couple years from now, you want to update your project and change this little line of code to make it work on the latest browser. Maybe you have the perfect person to do it in-house, but do you have the right to do it? With Klynt Player, we made sure we use only open source code so that you are free to change everything you like without infringing any copyright.

- What kind of documentation do I have access to? If you are serious about the perenity (and stability) of your interactive project, one of the first things you should do is have someone check the quality and readability of the generic source code. If this 10000+ lines+ source is badly written and explained. Forget it.

In anyway, if you are curious about this, ask a developer around you if you can to have a look at the documentation of the code (ours is on github) to give you his feedback.


Any feature missing out there? Tell us what would make the difference for you. We are always busy improving Klynt and your feedback is important to us.