Since last summer I have been intrigued by this quasi-no roadmap concept from Roam. But now almost a year later, I actually don't think it's a good strategy. @Conaw maybe now is a good time to lay out a plan with the public and timelines.
I see value in the "no roadmap" approach during prototyping & beta, but as the product matures & tackles larger problems, people want to understand what they are investing in. People using a product is an investment. Is the bank going go grow their money, or gain little interest?
Without a roadmap that outlines general goals, how can a team set priorities? how can they design for the future? Databases for example cannot be easily changed, especially when it comes to security, performance and optimized search.
Without a roadmap, it is a little like "design by my mood". This is investing based on emotion, not logic. Not a financially sound technique.
We would like to see a Roam roadmap. Let me highlight some things that make people feel like Roam is a "good bank" for their thoughts.
Roadmap features:
+ New backend DB designed for larger data - Planned early summer 2021
+ Permissions model for the database, allowing granular permission control by user and group. - planned end of summer 2021
+ Hiring a chief information security officer (ASAP)
+ Third party security testing - planned summer 2021
+ Full text search optimization - end of summer 201
+ UX performance enhancements - ongoing
+ Editable tables - some time period ...
+ Usable visual graphs of our graph db
+ REST API for server access by end of 2021
+ Client API finished by????
and other things. Let's look at the competitors (who are quickly catching up to Roam).
It doesn't need to be complex, but provide clear direction. The Roam White Paper (roamresearch.com/#/app/help/pag…) is truly brilliant and really lays out a long-term vision.
Even so, shorter term specifics would be very welcome.
So what about it? Can we get a 2021 roadmap? I can only imagine that the internal dev team has a short-term roadmap, maybe reveal some of the specifics with the public.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Roam announced local graphs are available to all Roam customers & many ask for best practices advice. Here are some recommendations. Thanks for help: @elaptics@zsviczian
2/ What is a local graph? It is a Roam database that you create on your computer in a browser. That database lives only on that computer & only in that browser. The data in your local graph is never transmitted to Roam's servers. Theoretically you can have unlimited local graphs.
3/ In fact, if you create a local graph on your computer in Chrome, and then on the same computer you open FireFox, FireFox can't see that local graph because that graph lives in the permanent cache of Chrome and is only visible there.
2/ When I saw this I thought "information overload", if he is trying to sell @obsdmd, he isn't helping." I was wrong again! As I say, always learning from community. I love the sidebar.
but always felt it would be useful to have more freedom.
3/ I wrote some code that "detached" sidebar window panes so I could move them and dock them into other places. It looked great and I could see value in it. However, this was a real hack and destabilized Roam. Not Roam's fault, I was "surgically repositioning their right arm".
1/ EMOTIONS & NOTES? One thing that fascinates me about Tools for Thought (@RoamResearch, @obsdmd, @rem_note & @logseq) are the deep emotional connections people make with these tools. But it isn't about the tool, it's about the "thoughts" captured in these tools!
2/ When I started using these tools, I thought people used them because of their features & that really one tool was likely better than another. The truth is they each have advantages. Let me list what I see:
+ Roam: Great graph DB outliner with strong linking
..cont'd
3/
+ Obsidian: Great Markdown editor designed for thought, leveraging speed of local hardware
+ Remnote: integrating spaced learning into its DNA with roots in education
+ Logseq: opensource tool based on graph DB & markdown. Totally unique hybrid that has a solid future.
1/ Over a year ago I tried out Obsidian. At the time I found it to just be another Markdown editor. I was actually frustrated with the @obsdmd devs because it seemed like a shift from @DynalistHQ which is a fabulous product, but needing love. Well I was wrong, they were right
2/ In recent months I have seen many dear friends move to @obsdmd from @NotionHQ, @RoamResearch and other such tools. I honestly thought they are crazy (Ok they are and they know it.) But they are so happy with Obsidian and brag about it like teenagers in love, it is irritating.
3/ But I have to say, these friends, some former Roamans, are really good, smart, hard working and caring people. I told myself, there must be something to @obsidian if these individuals are so happy. They know me, I know them. They would not waste my time.
1/11 Spaced Repetition (SR) is amazing for learning. With it, I learned 2nd language. I wish I had this article by @andy_matuschak when I started. His article: [How to write good prompts: using spaced repetition to create understanding](andymatuschak.org/prompts/) #roam
2/11 Advice from real world experience. I admit, earlier I would have been too stubborn to listen. I am ready now & advice came just in time. Thanks Andy! We may not be friends in real life, but I hope to be twitter pals when you start to use @roamresearch (It's going to happen)
3/11 Let me share some of my highlights and personal takeaways. PLUS: please share your advice with me of lessons learned from your own experience with SR.
So Andy's article is a long read, but well worth it. I recommend reading it a few times spaced over time.