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.

Status Submitted
Categories Atlas
Created by Samuel Irenikase
Created on Nov 14, 2026

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 you or your team?

Explain how the request adds value or solves a business need.


What steps, if any, are you taking today to manage this problem?