Context:

November is just around the corner and Evernote integration is my next priority. While we all know that Kneaver is notes on steroid, the reality is that most Kneaver evaluators have been using Evernote for years already. Legacy beneft is on Evernote side and  have better do with it and provide a top integration with it. In the spirt of #WOL and making my work observable I’m willing to gather early feedbacks and let my priorities be led by yours.

Objectives

• Let users work on a note stored on Evernote indifferently from Evernote or from Kneaver. benefit is easing the workflow and avoiding endless overthinking of where to start writing. A note can start on Evernote and later be reused and weaved inside Kneaver. Allows also to tap into the vast corpus of notes already available instead of starting again from scratch.
• Use Evernote as a backup storage for Kneaver, main user benefit being peace of mind Kneaver being a tiny enterprise.
• It must be easy to control oth from Evernote and from Kneaver.
• It must be 100% compatible with Evernote so that it integrates in the flow and preserve long term compatibility.
• Less than 10% of the a typical Evernote content has some reason to be visible on Kneaver.
• It must be fast and behind the hood. 

Use cases

This is how I see it.

Deepening in Kneaver

I’m on Evernote and I see a note I wish to build on in Kneaver. let’s say it’s a note I wrote with 10 ideas for future features.

1. I add a tag on the note “ForKneaver”. It can be any tag as long as you place it inside Kneaver settings along with other integration details. I tough also of “4K”, “4Knv”, “ToKneaver”. What is you favorite? better short, explicit? It would be nice to have the view of regular Evernote users. Use the comments below to send me your feedback.
2. Kneaver will bring the note within your space of the occasion of a regular synchronization. Synchronization happens when you connect or every 1/4 hour or 2 hours depending on your plan. 
3. The note will appear as a Topic item inside Kneaver. It will show up in your recents if it was changed recently in Evernote. It will be a regular item, you can change the type, build links and link to it. You can find it by search.
4. Inside the note there will be an attribute “knv:EvernoteBind” and an identifier to the Evernote note usable via the official API.
5. If later changes are done on Evernote they will be synchronized inside Kneaver and the note will change. Evernote content will correspond to the body of the Kneaver item. Links are outside of the body and will remain unaffected by synchronization.
6. Using Kneaver to establish links between items bound to Evernote notes is perfectly possible and is done as usual using the + icon.
7. Using Evernote bound items inside Mindmaps is also possible.
8. Adding Wikilinks inside an Evernote note wil be resolved as usual within Kneaver display but will not show as a link on Evernote. Kneaver has much more capabilities than Evernote.
9. Editing a bound item inside Kneaver is possible and will update the corresponding notes instantly after. 
10. Changes done in Evernote while editing the same item inside Kneaver will not be displayed and taken into account. However versioning will help fix those cases. A future release may support instant updates if it turns to be a critical need.
11. Body of the Evernote note will correspond to the raw body inside Kneaver (wikilinks not resolved but between double square brackets, no specific styles applied, no UI marks).
12. A bound item can be bound to a single Evernote item only and this note can reside in a single Evernote account only.
13. Two different items can be bound to two different notes residing in two different Evernote accounts. This would be a common case for team spaces with each user having items bound to his Evernote account. This feature is plan dependant.

What do you think of the feature as described via this use case? 

Do you have other uses cases to suggest?

What are your priorities in the those points? Is there a best way to chunk the work for more agile release cycles?

Backup in Evernote

During regular synchronization Kneaver will save inside a specific notebook all the items visible in your scope.

1. I imagine the default name of this notebook to be “FromKneaver” or “Kneaver’s Backup”. What you are your suggestions. Feel free to interact in the comments.
2. On a regular basis (depends on plan) Kneaver will scan all changed and new items and push them onto this notebook.
3. Title of the note will be the name on Kneaver
4. Body of the note will be the rendered item filtered to fit with acceptable HTML policy within Evernote as docuemented in their guidelines. This means that readability and reusability of the note will be favored over preserving internal Kneaver attributes. It’s an export backup not a mirror. 
5. Links will be exported as HTML links.
6. Pictures will not be exported in the first iterations, links to existing pictures will be supported.
7. Sub items like fragments will be aggregated to their owning items. They will not be exported on their own as independant notes.
8. Other Inline items will be embeded as they would in a Kneaver display. They will also be exported on their own.
9. Subsequent backup will update existing notes if they exist.
10. The system is arranged to support exporting to multiple Evernote account.

What dyou thing of this use case? Would it provide you a complete peace of mind ?

What would you need first if this use case was going to be implemented in several iterations?