Useability and fitness for purpose of Bambu Suite in it current state
I posted this on Reddit just as you see below, and I was told it belonged here:
I know it is long. And I had a few TLDR responses to it.But I would like for there to be discussion about this… In my working life as an engineer from the 1960s up till I hit retirement age, I was heavily involved in alpha and beta testing and QA with both hardware and software. So my background can be considered out of date.
I have been told not to bother the team with support at support@service.bambulab.com.
With this, I would like help amending it and to find out where to send it.
With each new addition to the H2 line, ( I had my X1C via the kickstarter, And I recieved my H2C Laser about 10 days ago) will be new folks trying to come to grips with this for the first time, and from my perspective, Suite is not up-to-that level; or indeed even close to the bar that Bambu set for themselves with Studio we are at almost the one year mark since Suite was released and still needs a lot of work to get it to the level that Studio gave us at that point in its development
with Studio, we have solid tutorials and a path in Bambu Lab Academy that is far better than that they have provided for Suite.
And while not directly on Bambu’s plate, the third-party support/YouTube videos, etc.: was by comparison vast compared to where we were at the one year post-release for Studio.
For example: for Studio; BL acad. has 3 sets of lessons with 9 Beginner and 9 Intermediate and 6 lessons at the Advanced lesson level.
For Suite, we are offered; BL acad. has 3 sets of ‘lessons with 9 Beginner and 6 Intermediate and 7 lessons at the Advanced lesson level. which looks like a fair allocation of resources, but for me, the large problem with teaching Studio this way is that the software is IMO not fit to have the Bambu Lab brand on it in its current state:
The biggest hurdle to me resides in its sloppy porting to macOS:
On macOS, Bambu Suite does not follow expected platform conventions. Standard application menus for common operations (selection, grouping, object management, etc.) are absent. The menu bar provides little more than a “Services” entry, which itself returns “No Services apply.” This leaves users without familiar navigation paths and significantly increases friction.
This is an email I have been preparing to send to Bambu Support, and I would like to know what others who have just started to learn how to use their laser and their cutter feel about it, and to put forward any edits to improve and/or correct it. I have had no experience with other software of this sort. The lack of macOS standard menus, etc., knocked me for a loop. Feel free to laugh at me, but I am almost 80, and learning new things such as Studio has been an uphill climb since I started on it this week.
But: I had no problems picking up Bambu Studio and turning out quality work with it within 2 weeks.
Lastly, is Support the right place to send it? Is there a human factors or user interface department that would be a better destination? My first draft letter is under the line.
____________________________________________
To Bambu Lab Support,
I am writing as a user of the H2C (10W) laser system and Bambu Suite, and as someone with a long technical background in computing and precision workflows. I would like to report several usability issues encountered during a real project and request improved documentation and onboarding for Suite, particularly for laser workflows.
In short: the current software is powerful, but key behaviors are undocumented, non-intuitive, and in several cases actively misleading.
While some of these issues may have been marginally acceptable at initial release, they are not acceptable at this stage in the product’s lifecycle.
During a straightforward sign design (vector import, text layout, fill engraving, and cut), I encountered the following:
- Object Visibility vs Processing State
Objects can be visible on the canvas yet disabled for processing (greyed in the Objects panel with a slashed eye). This distinction is not clearly explained anywhere. The result was that only one text element processed while the rest of the design silently disappeared at “Prepare.”
- Hidden / Implicit Selection or Isolation State
At one point, only a single object remained editable, while all others appeared greyed out and unresponsive. There is no clear indication that the user has entered a restricted selection or isolation mode, nor how to exit it.
- Group Handling and Imported SVG Behavior
Imported vector artwork was placed into grouped containers that became partially inactive. The relationship between parent groups and child objects is unclear, and the UI does not make it obvious when a group is preventing interaction or processing.
- Inconsistent or Misleading UI Affordances
The interface displays scaling percentages but does not allow editing them, requiring manual dimension calculations instead. This is counter to standard vector software expectations.
- Poor Discoverability of Critical Controls
Key controls (such as enabling/disabling objects for processing via the eye icon) are small, imprecise targets and not explained in tutorials or the wiki. This caused significant delays during time-sensitive work.
- Lack of Standard macOS Interface Conventions
On macOS, Bambu Suite does not follow expected platform conventions. Standard application menus for common operations (selection, grouping, object management, etc.) are absent or effectively non-functional. The menu bar provides little more than a “Services” entry, which itself returns “No Services apply.” This leaves users without familiar navigation paths and significantly increases friction.
- Lack of End-to-End Tutorial for Laser Workflows
There is no clear, step-by-step guide covering:
- Importing vector art
- Managing groups and layers
- Assigning process types (fill vs line)
- Ensuring all objects are active for processing
- Verifying output in the Prepare stage
Given that the H2 series is now well into its lifecycle, this level of friction is not acceptable for what is otherwise excellent hardware.
I would strongly recommend:
- A comprehensive “first project” laser tutorial (video + written)
- Clear explanation of object states (visible vs process-enabled)
- Improved UI feedback when objects are disabled or excluded
- More standard scaling controls (including editable percentage scaling)
- Better group/layer visualization and control
- Alignment with standard macOS interface conventions
I offer this feedback constructively. The hardware is impressive, and with improved software clarity, the overall system could be exceptional.
If helpful, I would be glad to provide additional notes or walkthroughs of the issues encountered.
Regards,
Mustrum