Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

All feedback

Title: MongoDB Atlas Mobile Responsiveness Issues — Screenshots and UX Feedback Hello MongoDB Product and Engineering Team, I'm reaching out to share constructive feedback about the mobile browser experience of MongoDB Atlas. While accessing my Atlas project through an Android smartphone, I encountered several responsiveness problems that significantly affected usability. I've included screenshots demonstrating the issues. Observed problems: 1. Horizontal overflow: Important dashboard sections extend beyond the phone's viewport, leaving text and interactive elements clipped. 2. Broken button responsiveness: Buttons such as "Add Current IP Address" and "Do not show me again" become awkwardly positioned, with text wrapping excessively. 3. Unnecessary empty space: Large sections of the screen are unused while essential controls remain difficult to reach. 4. Cluster management layout: Configuration cards, actions, and information panels do not consistently adapt to narrower displays. 5. Navigation friction: Some operations require horizontal movement to access controls that should be visible within the screen. Suggested improvements: - Introduce responsive mobile layouts for dashboard and cluster management screens. - Use vertically stacked cards and actions on narrow screens. - Apply proper text wrapping and prevent viewport overflow. - Improve dialog, notification, and button responsiveness. - Test common Android and iOS viewport sizes. - Prioritize important mobile workflows such as database monitoring, project navigation, and configuration review. I understand that Atlas is a sophisticated developer platform, but I believe its core operations should remain accessible on smartphones, particularly for developers who occasionally work without a desktop computer. I'm sharing this feedback voluntarily, without seeking financial compensation, employment, or any other benefit. I hope the attached screenshots are helpful to your product and engineering teams. Thank you for your consideration.

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...
Samuel Irenikase 1 day ago in Atlas 0 Submitted

Title: Improving MongoDB Atlas responsiveness and usability on mobile browsers Hello MongoDB Product and Engineering Team, I'd like to share some constructive feedback regarding the usability of MongoDB Atlas on mobile devices. Atlas is an important tool for developers, and I believe its browser interface could become more accessible for people working from smartphones and smaller screens. Although Atlas has received significant interface improvements, I would encourage the team to review the complete mobile experience, particularly navigation, Data Explorer, database collections, monitoring dashboards, and project settings. Problem Developers sometimes need to inspect collections, monitor database activity, review alerts, or manage projects when they don't have access to a laptop. A desktop-oriented interface can make these workflows difficult on smaller displays, particularly where layouts require horizontal scrolling or complex navigation. Suggested improvements - Introduce mobile-first layouts for essential Atlas workflows. - Adapt Data Explorer's tables, filters, navigation, and document viewer for smaller screens. - Prioritize cluster health, alerts, and read-only database inspection. - Improve touch targets, menus, dialogs, and form accessibility. - Test Android and iOS browsers at common screen sizes. - Preserve existing functionality while progressively enhancing mobile support. Why this matters Improved mobile accessibility would make Atlas more convenient for developers, students, small teams, and engineers working in environments where mobile devices are sometimes their primary means of accessing online services. I'm sharing this voluntarily as constructive product feedback, without requesting compensation, employment, or any commercial arrangement. Thank you for considering the suggestion.

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...
Samuel Irenikase 1 day ago in Atlas 0 Submitted

.

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...
Jeffrey Cheak 3 days ago in  0 Will Not Implement

Permission "Backup Read Only" role for Ops Manager API Keys

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Application teams want to report on backup history/retention and success/failure rates of backups for monthly business rep...
Ryan Hoeksema 3 days ago in Metrics & Observability 0 Submitted

Restore a collection from snapshot using Atlas on collections using Queryable Encryption

What problem are you trying to solve? Atlas collection-level restore does not currently support Queryable Encryption (QE) collections What would you like to see happen? Queryable Encryption (QE) collections Why is this important t...
Sam Potter 3 days ago in FLE and Queryable Encryption 0 Submitted
131 VOTE

Include Problematic Query Details Directly in Query Targeting Alerts

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. When Atlas sends an alert such as "Query Targeting: Scanned Objects / Returned has gone above threshold", the notification...
Sooya Park 9 months ago in Atlas Monitoring, Alerts & Observability 1 Planned

Add metric for Data Federation quota limits

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Data Federation currently exposes quota information through the web UI and API, but it is not readily available as a metri...
Dawid Pierwola 2 months ago in Data Federation 1 Future Consideration

Backup Policy based on individual Database Instead of overall cluster backup

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We do have backup policy strategy for the cluster level within the atlas MongoDB however we need to perform the backup bas...
Bathula Sai Reddy 6 months ago in Atlas Backups 1 Will Not Implement

Feature Request: Expose IOPS Utilization Percentage Metrics in Datadog Integration

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We would like to request the addition of IOPS utilization percentage metrics to the MongoDB Atlas Datadog integration.Curr...
Ariel Fernandez 5 days ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Restore Tabs and Queries When Reconnecting to a Saved Connection

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. When working with multiple MongoDB connections in Compass, I often open several collections, queries, and other tabs withi...
Refael Abramov 19 days ago in Compass & Data Explorer 2 Submitted