Smart Plugins on mobile
Smart Environment can defer loading on Obsidian mobile.
Current detailed mobile screenshots and control placement require a fresh recapture before they should be treated as publication proof. Use the capability boundary below instead of relying on older step-by-step images.
Readiness workflow
- Open the Smart Plugin workflow you intend to use.
- When Smart Environment shows Smart Environment not loaded or Idle, select Load Smart Environment.
- Keep the available loading or status view open.
- Wait until it shows Smart Environment ready or Ready.
- Run one small plugin action.
- Verify the actual result separately.
A Ready status proves that the Environment reached its current ready state. It does not prove that every plugin, provider, model, source, or mobile gesture works correctly.
Why mobile can differ from desktop
- Mobile does not provide the same persistent desktop status-bar surface.
- Startup, memory, battery, and background-execution constraints differ.
- Some desktop-only workflows require Electron webviews or direct filesystem access.
- Control placement can vary by Obsidian, operating-system, and plugin release.
Use the controls visible in the installed mobile build rather than searching for a screenshot-specific button.
Feature boundaries to review
| Workflow | Mobile expectation |
|---|---|
| Connections and Lookup | Wait for Environment readiness, then verify one actual result. |
| Context using in-vault notes, blocks, and named contexts | Can remain useful; verify clipboard behavior in the destination app. |
| External files and folders | Desktop filesystem access is required. |
| Provider chat codeblocks | Saved links can remain useful, but full embedded webview behavior and automatic URL capture are desktop-dependent. |
| Pro API Chat | Treat model, storage, and sync behavior separately from Markdown provider bookmarks. |
| Connect Pro | The running Obsidian Desktop vault remains the execution side. |
Deferred loading FAQ
Is deferred loading on mobile a bug?
No. Smart Environment can defer loading on mobile. Select Load Smart Environment, wait for Ready, then test the first plugin result separately.
How do I know Smart Plugins are ready?
Use the current status view until it reports Smart Environment ready or Ready. Then run the smallest useful action and inspect the result.
Why are older mobile screenshots not shown here?
A screenshot proves only the build and state it captured. Current mobile control placement needs a fresh, matched-state recapture before it can support current instructions.