January 12, 2020
This is note 2 of 5 in a series on publishing automation.
Above - Publishing from Bear to this website. Dreams do come true ❤️
To boot, I and a lot of other people are most productive when writing in Bear. So naturally, wouldn’t it be great if we could use Bear to publish to other platforms, like the website you’re reading right now? I think yes, but there are obstacles:
Bear ships on iOS, macOS and watchOS — not on Android or Windows, but a web app is forthcoming. The team is very clear about their priorities, and adding integrations to Bear isn’t one of them. However, this focus is clearly why Bear is so great. Thus, there’s no officially supported way to use Bear as an authoring tool for other platforms. Unless of course you count WordPress for iOS, which recently added functionality to publish from Bear and only works if you’re using WordPress to start with. More info on that here.
App Sandboxing makes the Apple ecosystem much safer than the Android ecosystem, but it also makes it much more difficult for apps to integrate with one another. That means if Bear doesn’t ship with functionality to publish to another platform, good luck trying to pull that off. It does however support the x-callback-url protocol and clearly documents the interfaces, but while this is very nice compared to other native iOS/macOS apps, it’s still much less accessible than having an actual REST API to call.
Until Shiny Frog ships a way to build off of Bear as an authoring tool, the best way to make it a reality to is build this pipeline yourself. In the next few articles I’ll talk in greater depth about how I did just that:
Previous articles in this series: