Something on your mind?

Share it and help shape the future of Quick Draft

Planned

Error on Post-Processing (Refine option)

First of all, congratulations on the nice app! Truncated File Extension during Image Post-Processing in Quick Draft for iOS Environment and Context Application: Quick Draft for iOS. Integration Target: Obsidian Vault synchronized via iCloud Drive. Observed Error: "Resource not created" (or "O recurso não foi criado") within the Obsidian interface. Issue Summary A critical failure in the file-writing routine of the Quick Draft application occurs when utilizing the "Crop" tool within the "Refine" menu. While standard image captures are correctly persisted with a .jpg extension, images subjected to a "Crop" operation are saved to the file system as raw UUIDs without a file extension. This metadata truncation prevents Obsidian from identifying the resource as a valid media attachment. Steps to Reproduce Initiate an image capture using the Camera or Scanner tool within the Quick Draft interface. Select the Refine option on the capture preview. Execute a Crop operation to adjust the image dimensions. Commit the draft to the Obsidian destination (e.g., obsidian-ios-v2). Observe the resulting link in Obsidian, which appears as ![[UUID]] without an extension. Observed Behavior and Root Cause Analysis Extension Truncation: The application's History log confirms that standard saves yield filenames such as B626...8B7A.jpg, whereas saves following a "Crop" action yield truncated filenames like 8FA2...8FA5. Obsidian Resource Resolution: In the absence of a file extension, Obsidian treats the transcluded link as a reference to a non-existent Markdown file rather than an image. Manual Validation: Manually appending a .jpg extension to the affected file within the iOS "Files" app restores correct rendering in Obsidian, confirming that the "Crop" module fails to re-append the MIME-type extension during the final write operation. Expected vs. Actual Results Expected: The application should preserve the .jpg or .png extension during the re-serialization of the image object after an edit. Actual: The "Crop" operation triggers a loss of file extension metadata, resulting in broken resource links in the target Obsidian Vault.

An Anonymous User about 1 month ago

In Progress

Full-screen route grid

I use many routes for different capture categories like journal, health, shopping, ideas and so on. The current routes bar at the bottom works but does not scale well when you have 10 or more routes. The tiles are small and require precise tapping, and it is hard to scan quickly. When I open Quick Draft I already know exactly what I want to capture. The route selection is not friction for me, it is the first intentional step. My ideal workflow is simple: open the app, see the categories, select one, write. Large tiles with icons would make this instant, as I can recognize the category visually without even reading the label, reducing friction further. A full-screen grid of large tappable tiles would make picking a route much faster, especially with many routes. Each tile would show the route name and an emoji or icon for instant visual recognition. As a nice to have, tiles could be sorted by frequency of use, with the ability to pin the most important ones to fixed positions at the top of the grid. This feature could be optional, enabled in settings for users who want the category-first workflow, and disabled for users who prefer to jump straight to writing and categorize later via the existing bottom bar. The current bottom bar without icons adds more friction than a full-screen grid would, because the route still needs to be chosen regardless, just with smaller and harder to scan targets.

An Anonymous User 3 months ago

2

Planned

Tag insertion

I use a route that appends to my daily journal note with a horizontal line after each entry. I like to add Obsidian tags at the top of each entry like #health or #ideas to classify captures so I can search and filter my journal later. I often use voice input to capture notes, but tags still need to be typed manually every single time. This breaks the flow completely. It is repetitive and error-prone on mobile, as a typo means the tag won't match in Obsidian. The existing H toolbar button is almost what I need, but it inserts a trailing space after # which creates a markdown heading instead of a tag. The simplest fix would be a toolbar button that inserts # without a trailing space. As a first nice to have, pressing it could show a searchable list of previously used tags so I can tap a tag instead of typing it, making repeated tagging fast and consistent. As a second nice to have, since tags are one of the core ways to organize and navigate notes in Obsidian, it would be great to have proper tag management: pinned tags always appearing at the top of the list, the rest sorted by frequency of use, and a settings screen to add, edit, pin and delete tags. This would make Quick Draft a first-class citizen in tag-heavy Obsidian workflows. As a note, my current workaround is to create a separate route for each tag, where the template wraps the content with the relevant tag at the top. This works but causes the number of routes to explode quickly, mixing the concept of routing to a destination with the concept of tagging content.

An Anonymous User 3 months ago

2

Planned

Multiline indentation support for {{content}} in Quick Draft templates

Hi, thank you for this great app! I’d like to request an enhancement to Quick Draft’s template system regarding multiline content handling. Currently, when using {{content}} in a template, multiline input is inserted as raw text. This means that if the template applies indentation or list markers (e.g. "- "), only the first line is formatted, and subsequent lines lose indentation. Example template: - {{HH:mm:ss}} {{content}} If {{content}} contains multiple lines, only the first line is indented. This makes it difficult to create readable structured logs (e.g. bullet lists with timestamps). Feature request: - An option to apply a prefix or indentation to *each line* of {{content}} - Alternatively, a variable like {{content:indent=2}} or {{content:list}} that reformats multiline input line-by-line - Or a setting to automatically re-indent multiline content to match the template context This would greatly improve Quick Draft → Thino / log-style workflows, especially on Android where OS-level text preprocessing (like iOS Shortcuts) is not available. Thanks for considering this!

An Anonymous User 4 months ago