Skip to content

Atlas App Services

← MongoDB Feedback Engine

How can we improve the Atlas App Services?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

43 results found

  1. Search Across Functions Code in Cloud UI

    In writing any app, there are likely to be multiple Functions stored. A developer should have the ability to search for specific snippets or text elements across all Functions.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Developer Experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Support for Twitter Authentication

    Currently, you only support Google and Facebook for social logins. Can Twitter also be added?

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Developer Experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Human readable URLs in UI

    Currently, the app urls are extremely long and unreadable, for example: https://realm.mongodb.com/groups/5ab028594e6581148629dc65/apps/5b28f4615fdce07a74cd7f50/triggers/5bcf226fe707c05350750dcc
    This looks pretty ugly. It would be a lot more user friendly to:
    - eliminate the /groups/<groupID>/ portion of the URL entirely - the app ID already uniquely identifies the group anyway
    - use the clientAppID instead of the raw objectID for /apps/<appID>.
    For example, the above URL could instead be represented as
    https://realm.mongodb.com/apps/my-app-xyz/triggers/5bcf226fe707c05350750dcc
    with no loss of functionality or precision

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Developer Experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 3 Next →
  • Don't see your idea?

Atlas App Services

Categories

Feedback and Knowledge Base

(thinking…)