Making plugin for mobile

Your plugin will be bundled as an advanced Markdown renderer option

Extending Markdown renderer in the mobile app is also supported by the similar way as the desktop app. But as Apple prohibits loading dynamic scripts that change the app's functionality, it has to be bundled at the compilation time. Plugins are displayed as "Advanced Markdown renderer options". So, basically, it is for adding features for the Markdown renderer like math.

You can extend the editor part since it is web-based. Extending functionalities of outside the webview is not possible. The below diagram illustrates its architecture:



You can build a plugin just as you build for the desktop app. Read the tutorial here to learn how to build a plugin for desktop. But there are some limitations. As the above section mentioned, you can only extend Markdown renderer with plugin.

There is inkdrop global variable which provides only the following prooperties:

Markdown renderer module is available.

If you have LESS stylesheets in a plugin, it will be pre-compiled into CSS. Similary, your ES6 JavaScript will be compiled beforehand.

How to register your plugin

There is not a plugin registry like ipm. You have to make a pull request to the plugin repository. Here is a step-by-step instruction for adding your plugin into the mobile app.

Update your plugin for mobile


It is a documentation for mobile. Basically you can reuse your but you have to remove sections for desktop like "How to install".

Remove "plugin" words from your plugin description

You can not use "plugin" or any words like "extension" in your package description or readme. Because your plugin will be displayed as one of renderer options like so:

Advanced markdown renderer options

Make a fork of inkdrop-mobile-plugins

Fork inkdrop-mobile-plugins repository. Then, clone it:

git clone<YOUR_FORK_OF_inkdrop-mobile-plugins>.git --recursive
cd inkdrop-mobile-plugins

Add submodule

Plugins are stored in ./packages directory as git submodule. Run the following command:

git submodule add <YOUR_PLUGIN_REPO_URL> packages/<PLUGIN_NAME>

Edit package.json

Add your plugin to devDependencies like so:

  "devDependencies": {
    "math": "file:packages/math",

Then, run npm install.


Run the following command:

npm run build


Add a test for your plugin to test/index.js to make sure it gets loaded properly.

For example:

test.serial.cb("mermaid", t => {
  global.window.inkdrop.packages.setPackageMainModule = (name, p) => {, "mermaid") instanceof Object, true) p.activate, "function") p.deactivate, "function")


Then, run the test:

npm t

Did it work? Okay, now it's time to make a PR :)

How to debug your plugin

Build plugin metadata:

npm run build:index

Launch webpack server:

npm run dev:server

Then, open up a debugger tool:

Open Developer Tools and you should see like this:


Can you help us improve these docs?

The source of these docs is here on GitHub. If you see a way these docs can be improved, please fork us!