Something on your mind?

Share it and help shape the future of Quick Draft

Planned

{{content}} v {{title}}

I’ve got two Routes/Destinations setup for task management, one for Work and other other Personal. They’re a simple one-line capture of the task, routed and tagged appropriately so i can filter inside Obsidian. I’m trying to build a standard “note capture” Route/Destination, but I cannot seem to get it to work. It doesn’t replace {{title}} with the first line of the text I entered. Let me rephrase…it uses the first line as the filename, which is great. I have a metadata field called “Name” whereby the filename/title is captured here as well. AND I have a Header 1 at the beginning of the file so that it’s big and bold when I reopen the file in the future. It’s those latter two which don’t replace {{title}} with anything. Is this meant to be?

An Anonymous User 16 days ago

1

New icon suggestion!

Hey, awesome app! I only have a minor gripe, as a graphic designer: I think the icon could use some personality and look a bit less generic! Also, it’s not optically centered, which bothers me a little :) Instead of just complaining though, I came up with something - see attached image. You can see on the left the bare icon, and on the right an example on how to center it, for instance in a squircle for balanced look. This proposition I think illustrates the concept of a quick draft a lot better: we keep the general idea of a square with something going into it (as in, putting content into the note), but we replace the arrow with a pencil, and evoke the idea of a draft with dashed lines. On top of that I added the idea of quickness with some speed lines I have also picked the purple shade directly from Obsidian’s website for the icon to be more recognizable to obsidian users and to look more harmonious when put side by side with the Obsidian app. If you like it I can provide the source files / SVG for you to implement - all for free of course, I’ll just be happy with my homescreen having a better looking icon haha. If you like the concept and would like some modifications I’ll be happy to do them as well. Hope you like it, have a nice day!

An Anonymous User about 1 month ago

1

Completed

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 3 months ago