Sorry, we don't support your browser.  Install a modern browser

API for Plug-in Development#101

I would love to be able to create plug-ins, macros or “algorithms for thought” for Scrintal.

2 years ago
Changed the title from "API for plug-in development" to "API for Plug-in Development"
2 years ago

I agree with this in principle but also have a little wariness. I certainly agree with having the means to pass data to and from scrintal via apple shortcuts for instance and url schemas (eg same way as things3 Bear) but I’d be wary of creating a situation like obsidian where you could end up having a great well crafted well thought out app buried and diluted under a mountain of plugins.
Be clear on what scrintal is for and then do it really really well rather than be pack horse for add-ons
This said if the plan is to make a Swiss Army knife then make it a moderate one rather than a rediculous 250 tool 30cm wide one :)
Obviously just a personal view

2 years ago

Scrintal is very unique in the market and if passes through beta stage successively, I think can even dominate it. But even now there is a huge bulk of feature requests probably you will not be able to catch up with. And plenty of them are very personalized, targets few people and it is not logical to develop them but they are needed by those people at the same time. And the reason why Obsidian is kinda a market leader is its customizability. So please consider an API. begging

2 years ago
Merged Support plugins#157
2 years ago

And not just an API for the Scrintal app (which would certainly be cool) but similar to Inkdrop with just support for community markdown plugins within the text editor.

Picturing base scrintal markdown editor becoming enhanced with plugins for math equations, in text table editing, diagram creation like mermaid, etc… would be very useful imo.

Probably would need to allow for a syntax editing mode and a preview mode. Maybe the default is the Scrintal editor (allowing for basic editing as currently implemented as well as an uneditable preview of the plugin products) but if someone chooses to directly edit the syntax they can switch modes and modify the raw text allowing them to engage with the plugin capabilities.

a year ago

From a user perspective, some would never use an API, but there would be a significant number of potential users who may never use Scrintal at all if there is no method to exchange data/text to and from Scrintal. And those power users would likely become some of Scrintal’s greatest evangelists.

Loyalty to the app is not going to be due to lock-in anyway so it is best, IMO, for the Scrintal team to embrace openness of data movement and to never consider it a threat to retaining a subscriber base.

Personally, my loyalty is probably good for decades based on that openness, but I’m reluctant to build out my second brain on Scrintal if the attitude is to lock us in. My desire is not the freedom to export everything from Scrintal (though I see bulk mark-down export is coming), but to be able to experiment and play with the input/output flow of ideas and information with Scrintal as my creative hub.

I’m not inclined to switch due to Scrintal’s unique design concept and head-start so I want to commit to a long future with this app, but I absolutely need to know the company wants to embrace the open exchange of data to do so.

I subscribed to support Scrintal, but I’m waiting to see what the approach is to inter-operability between Scrintal and other apps. I want to be able to move content/data between Scrintal and apps like Google Sheets or Notion or Airtable alternatives like Stackby.

Those intermediary apps allow me to do whatever I want to craft and mould my data for any purpose, but they are no substitute for Scintal’s experience as a creative input and study system. And they would allow me to focus on Scrintal’s purpose without getting sidestracked.

API’s and Webhooks will, IMO, greatly expand Scrintal’s market opportunties and grow the company, not expose it to the risk of losing subscribers. This is the age of data exchange and automations after all.

I’ve found there is a distinct difference between the companies that listen to this need from their users and the ones that feel overly protective of their IP and try to firewall their app from other apps. I usually stay away from the ones that exhibit the latter behavior.

My take is the companies that get on board with open systems are the ones that succeed and become market leaders. The ones that don’t get on board with the zeitgeist tend to fail or stay quite small in impact.

a year ago

I am a Obsidian plugin developer and PKM youtuber looking at Scintal. I think publishing an API is essential because the beauty and power of Obsidian come 90% from its community plugins. You can build a lot of functionality from community such that other apps will never catch up to you.

And to many people, publishing the API also means that they have the ability to manipulate their notes by themselves. Just knowing that they have the ability to that make them feel safe to use. Since this is a daily tool, I don’t want to spend time on anything that I don’t feel safe of using it.

5 months ago