Been thinking about the architecture behind @RoamResearch, where it's going, and how it fits into a larger toolbox.
Broke it out into the following layers:
∙ Database
∙ Service
∙ Presentation
Easier for me to think about it this way.
Broke it out into the following layers:
∙ Database
∙ Service
∙ Presentation
Easier for me to think about it this way.
Roam(an) Architecture
Thinking in terms of layers facilitates how Roam could evolve.
Mentally separating the database from the presentation layer (the UI) puts even more emphasis on a forth-coming API.
Thankfully this is a top priority for them:
Thinking in terms of layers facilitates how Roam could evolve.
Mentally separating the database from the presentation layer (the UI) puts even more emphasis on a forth-coming API.
Thankfully this is a top priority for them:
Import/Export
Currently we can manually import/export Markdown and JSON. This lays the foundation for human and computer structured data.
∙ Markdown - human-friendly
∙ JSON - computer-friendly
Currently we can manually import/export Markdown and JSON. This lays the foundation for human and computer structured data.
∙ Markdown - human-friendly
∙ JSON - computer-friendly
Sidenote re: Copy/Paste
I can't express how grateful I am that Copy/Paste works as seamless as it does!! (Thank you! @RoamResearch)
Copy/Paste is the universal API regardless of platform and works well on PC, Mac, mobile. 🙌
I can't express how grateful I am that Copy/Paste works as seamless as it does!! (Thank you! @RoamResearch)
Copy/Paste is the universal API regardless of platform and works well on PC, Mac, mobile. 🙌
BUT Import/Export & Copy/Paste are manual processes right now
An API would enable programatic import/export in addition to the manual process. Data can be sent/synced from your favorite app for X with minimal effort.
cough drafts cough
An API would enable programatic import/export in addition to the manual process. Data can be sent/synced from your favorite app for X with minimal effort.
cough drafts cough
Speculating here but once the Service Layer becomes accessible, Roam will be an even larger component of people's data ecosystems.
Looks like I'm not the only one thinking this.
Looks like I'm not the only one thinking this.
An API reduces friction of adding Roam to a users toolkit by leveraging existing apps.
Allowing mobile apps like @draftsapp, Jayson/@simonbs, @ToolboxProApp to communicate directly with the database opens up the type of data people will add to their database.
Allowing mobile apps like @draftsapp, Jayson/@simonbs, @ToolboxProApp to communicate directly with the database opens up the type of data people will add to their database.
And that's just mobile. I can't even imagine all the possibilities of what people will do when they can interface with an API on their computers using code.
The response to Roam embracing custom CSS is an indication of how much the community wants to tweak, enhance, and share their experiences. Imagine what it will look like with an API available!
Custom UIs leveraging the database
Custom UIs leveraging the database
Or new kinds of apps entirely! Apps that treat language in a different way than we currently do.
I'd like to see ideas like this realized using the Roam database as it's underlying structure.
I'd like to see ideas like this realized using the Roam database as it's underlying structure.
Deep speculation territory BUT…
What if an API allows us to reference other databases besides the one we're currently in?!
This is where I get really excited. Imagine being able to link between your own databases. Or public DBs of people like @visakanv or @anthilemoon
What if an API allows us to reference other databases besides the one we're currently in?!
This is where I get really excited. Imagine being able to link between your own databases. Or public DBs of people like @visakanv or @anthilemoon
Especially with the public works libraries that people are contributing to. Public Roam libraries being categorized by @RoamPublic
roampublic.com/directory/
roampublic.com/directory/
Roam Coding Language
The current Roam "code" is borrowing from a number of sources and is somewhere between syntax, markup code, a scripting language, and a coding language.
I hope this evolves to something defined.
Example:
The current Roam "code" is borrowing from a number of sources and is somewhere between syntax, markup code, a scripting language, and a coding language.
I hope this evolves to something defined.
Example:
Regarding the current version, @CatoMinor3, @rroudt and others are documenting what they discover.
Others like @Malcolm_Ocean and @Mappletons are combining syntax with CSS to create a form of code.
Defined code would grow out of a similar mindset.
roamresearch.com/#/app/roam-tri…
Others like @Malcolm_Ocean and @Mappletons are combining syntax with CSS to create a form of code.
Defined code would grow out of a similar mindset.
roamresearch.com/#/app/roam-tri…
This is a lot of speculation based on my understanding of the architecture and some wishful thinking.
But when you have this strong of a community spring up around a beta product, it's because people love the product and how it affects their life.
But when you have this strong of a community spring up around a beta product, it's because people love the product and how it affects their life.
Roam has brought me so much sanity in organizing my thoughts and life the past few months.
I've waited years for a personal knowledge management tool like Roam. Thinking about where it could possibly go is 🤯 ‼️
I've waited years for a personal knowledge management tool like Roam. Thinking about where it could possibly go is 🤯 ‼️
