[GH-ISSUE #567] [Feature]: Printer Page - Add a print button on the printer card #370

Closed
opened 2026-05-06 12:28:50 +02:00 by BreizhHardware · 3 comments

Originally created by @aneopsy on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/567

Originally assigned to: @aneopsy on GitHub.

Problem or Use Case

Current Quick Print UX

The existing workflow to launch a quick print requires too many steps and creates unnecessary friction.

  1. The user has to navigate to the file manager,
  2. upload a file through the upload dialog
  3. then search for and select that same file they just uploaded.
  4. From there, they open the context menu via the three-dot button, select print
  5. finally choose the printer and filament before confirming.

That's five distinct steps with redundant actions, especially having to re-locate a file immediately after uploading it, just to start a simple print.

Proposed Solution

Streamlined Quick Print UX

We want to simplify the printing workflow by reducing friction and unnecessary steps.
Proposed flow:

  1. The user navigates to the printer page, then clicks the print button directly on the desired printer.
  2. This opens a file upload prompt, once the file is uploaded, the print modal appears with the printer already pre-selected. From there, the user simply clicks print.

The whole process goes from four deliberate actions down to a seamless, guided sequence.

Bonus - Optional file saving:

The upload modal includes a "Save to File Manager" checkbox, enabled by default. Users can uncheck it to skip saving the file, which is especially useful for quick test prints and avoids cluttering the file manager with throwaway files.

Alternatives Considered

No response

Feature Category

File Manager

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @aneopsy on GitHub (Mar 2, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/567 Originally assigned to: @aneopsy on GitHub. ### Problem or Use Case ### Current Quick Print UX The existing workflow to launch a quick print requires too many steps and creates unnecessary friction. 1) The user has to navigate to the file manager, 2) upload a file through the upload dialog 4) then search for and select that same file they just uploaded. 3) From there, they open the context menu via the three-dot button, select print 5) finally choose the printer and filament before confirming. That's five distinct steps with redundant actions, especially having to re-locate a file immediately after uploading it, just to start a simple print. ### Proposed Solution ### Streamlined Quick Print UX We want to simplify the printing workflow by reducing friction and unnecessary steps. Proposed flow: 1) The user navigates to the printer page, then clicks the print button directly on the desired printer. 2) This opens a file upload prompt, once the file is uploaded, the print modal appears with the printer already pre-selected. From there, the user simply clicks print. The whole process goes from four deliberate actions down to a seamless, guided sequence. ### Bonus - Optional file saving: The upload modal includes a "Save to File Manager" checkbox, enabled by default. Users can uncheck it to skip saving the file, which is especially useful for quick test prints and avoids cluttering the file manager with throwaway files. ### Alternatives Considered _No response_ ### Feature Category File Manager ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:28:50 +02:00
Author
Owner

@maziggy commented on GitHub (Mar 2, 2026):

What's about making the printer card a file drop zone? Not sure, but it just came to my mind.

<!-- gh-comment-id:3982375189 --> @maziggy commented on GitHub (Mar 2, 2026): What's about making the printer card a file drop zone? Not sure, but it just came to my mind.
Author
Owner

@aneopsy commented on GitHub (Mar 2, 2026):

I thought about that, but I found a couple of pros and cons.

Pros:

  1. Very intuitive for power users, drag a file directly onto a printer card and you're ready to print.
  2. Skips the file upload prompt entirely, making the flow even faster.
  3. Feels modern and aligns with common UX patterns (like dropping files into a chat or email).

Cons:

  1. Drop zones typically need a visual indicator (icon, dashed border) so users can identify them. Adding this to the printer card could feel cluttered, and without it most users would never discover the feature.
  2. Drag and drop works well on multi-monitor setups or non-fullscreen windows, but on a single screen managing windows to perform the drop often takes more effort than just clicking a button.
  3. Mobile users can't benefit from it at all.

I can implement both options so we can test them and evaluate later whether they both still make sense to keep.

<!-- gh-comment-id:3982502909 --> @aneopsy commented on GitHub (Mar 2, 2026): I thought about that, but I found a couple of pros and cons. Pros: 1. Very intuitive for power users, drag a file directly onto a printer card and you're ready to print. 2. Skips the file upload prompt entirely, making the flow even faster. 3. Feels modern and aligns with common UX patterns (like dropping files into a chat or email). Cons: 1. Drop zones typically need a visual indicator (icon, dashed border) so users can identify them. Adding this to the printer card could feel cluttered, and without it most users would never discover the feature. 2. Drag and drop works well on multi-monitor setups or non-fullscreen windows, but on a single screen managing windows to perform the drop often takes more effort than just clicking a button. 3. Mobile users can't benefit from it at all. I can implement both options so we can test them and evaluate later whether they both still make sense to keep.
Author
Owner

@maziggy commented on GitHub (Mar 2, 2026):

I agree.

<!-- gh-comment-id:3982514939 --> @maziggy commented on GitHub (Mar 2, 2026): I agree.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#370
No description provided.