Skip to main content

Filter by idea status

10000+ Ideas

antonina_7810Participant

Welcome to the app that destroys expensive monitors!Open for Voting

Subject: Adobe Needs to Address Burn-In Risk and Prioritize User ConcernsI’ve been using Adobe products for years, and while I can appreciate the innovation and range of features the suite offers, I can’t help but feel that many recent decisions are being driven purely by profit — with very little actual care for the user experience.Let’s be honest: the updates lately have been lackluster. Bug fixes are slow, user-requested features are brushed aside, and UI decisions often feel disconnected from real-world usage. But there’s one issue I want to specifically call out — and that’s the persistent, bright white top bar in Adobe apps.In 2025, we are well into the era of OLED displays. These screens are favored for their stunning color accuracy and are increasingly common among creatives, especially those working in photography, design, and video editing. However, OLED comes with one major vulnerability: screen burn-in.This glaring white top bar that can’t be hidden or customized is a major burn-in risk for OLED users. After months of use — especially during long editing sessions — it leaves a permanent mark at the top of the screen. That’s real, irreversible damage to expensive hardware that many of us rely on professionally.This isn’t a new complaint. The issue has been raised countless times across forums, support tickets, and user feedback channels. And yet, Adobe continues to ignore it. Either they don’t care, or they don’t believe it’s worth addressing because it doesn’t directly increase revenue. Neither option reflects well on a company that claims to support creatives.At this point, it feels like Adobe is more focused on pushing new monetized features and subscription tiers than listening to its core user base. A simple fix — like allowing the UI color to be adjusted or the top bar to be hidden — could go a long way in showing users that Adobe actually values their workflow and hardware investment.Stop burning our screens and burning our trust. Fix the UI. 

dim1koParticipant

P: Something like Ctrl+C & Ctrl+V for masks in mobile appOpen for Voting

I would like to propose an improvement to Lightroom Mobile that enhances the flexibility of working with masks. Specifically, adding the ability to copy masks to a clipboard and apply them to other layers, both for blending and subtraction purposes. This feature would significantly increase the creative possibilities and provide users with more flexibility when designing graphical content.   By implementing this functionality, Lightroom Mobile would not only streamline the workflow but also cater to advanced users who seek precision and efficiency. It would empower creators to develop more complex and intricate designs directly on their mobile devices, making the app even more versatile.   Despite the remarkable advancements brought by the new AI features in Lightroom Mobile, which have elevated photo editing to a new level, there is still room for improvement when it comes to the flexibility of working with masks.   Masks are one of the main reasons I appreciate Lightroom, as they empower creative control. However, there are times when even basic functionalities are missing. For example, zoom restriction, which sometimes prevents precise manual detailing of smaller areas.   I hope the developers take these aspects into account, as they could significantly enhance the overall editing experience and bring even more creative flexibility to the app.

Save multilayer png/jpg smart objects as psb and automatically replaceOpen for Voting

If I open a smart object, add a layer I want to preserve and hit save, I sometimes get this error: "Can't save this document back to its original file format. Flatten layers and discard extra data as necessary then choose File > Save again. You can save the file using File > Save As, but the associated smart objects will not be updated." Such a self-aware error message! The devs seem to know exactly what I want to do and are offering workarounds rather than just doing what I want. So my suggestion is: do what I want! When I press ctrl+s, save the multi-layer smart object as a psb instead of a png/jpg, then replace all instances of the existing smart object in the original document while maintaining their translations/styles/filters/etc. Part of my confusion is that dragging a png or jpg into my file results in a png/jpg smart object, whereas if I ctrl+v paste it in then right click layer > Convert to Smart Object, I get a psb smart object. I do both interchangeably, and it's hard to know which format a smart object is before I crack it open and do a bunch of work on new layers I intend to preserve, only to hit this annoying error message which basically says "nah we know what you want but we're too lazy to do it". And it can be a LOT of work to go back and replace smart objects if they've been duplicated, scaled, styled, masked, filtered, and buried in groups.

sarah5E05Participant

Smart Object on import improvementOpen for Voting

I double-click a Smart Object, a new tab opens with the Smart Object in it, I make the changes I want, then I click Save, and instead of saving the changes and taking me back to the first tab, the JPEG or PNG Error dialog appears (Can't save this document back to its original file format. Flatten layers and discard extra data as necessary then choose File > Save again.) This issue has been posted in plenty of forums before, and while I completely understand that a JPG cannot sustain layers or other modifications, what is the point of having a Smart Object if it behaves like this? This is SURELY a bug and could be handled way better. If I import files into my Photoshop document as a Smart Object, then it should be.. a SMART OBJECT—not some ‘Embedded JPG You Cannot Edit’ nonsense. I’ve seen replies saying this is “normal behaviour” while patronizing people who rightly asked the question. I had to write my own script just to import multiple files into the same PSD and have them be directly editable without having to package them again into another Smart Object. Photoshop, FIX THIS. It’s super annoying. Nobody cares if the original file was a JPG a PNG or a WEBP—we’re going to re-export it anyway into whatever format we need. My suggestion? Whenever I drop an image into Photoshop, it should be converted into a REAL Smart Object—whether it’s inside a PSD or PSB container, nobody cares. What we need is simple:1. I drag an image into a Photoshop file.2. I double-click the 'smart object layer' of the image I just import it to edit it.3. I mask, add layers, type, or do whatever I need.4. I press Save, and the Smart Object updates seamlessly without any stupid dialogs halting my work flow.  That’s it. SIMPLE. Nobody cares that the file used to be a JPG or a PNG, and if they really do, then embed the container info so Photoshop remembers the original format when exporting. Not that it’s necessary at all.