The number 1 request on the Realm GitHub Issue Tracker by a country mile is for a native implementation of Realm for Dart and Flutter.

Currently on the roadmap for after August 2020, there are many who would like to see this sooner...

https://github.com/realm/realm-object-server/issues/55

Would be great to have Full text search support for Realm.

Users should have the ability to change their email address.
Applications cannot give the ability to users to change their own email address. Once a user is registered/created there is no way for such user to update/change their own email address.

Hello, how come there's not a method to change an user's password? Most authentication APIs would provide a method like

changePassword(userId, oldPassword, newPassword)

or similar.

Support for Vue / Nuxt

A flag to enable/disable cloud sync on Fully-synchronized realms.

This would be convenient if you're offering sync as a premium feature.

As requested in this Github issue: https://github.com/realm/realm-cocoa/issues/5334

This item is also called out within the current public roadmap: https://www.mongodb.com/realm#roadmap

Provide complete, end to end support for macOS in MongoDB Realm. It will bring enterprise level capability to the desktop and allow total integration across (Apple) devices. Imagine a large factory where the workers can use their iPhones track or report work progress and then management being able to review those reports on their desktop.

Trying to use google authentication i have followed the documentation and the login flow works but because the redirect is mongodb.com url the google consent screen shows logging into mongodb which for the end user is going to be a redflag because that is not what they are signing in to.

Enable the use of gridfs with stitch apps in android.

It would be nice to be able to have built in client device presence support in Realm. Firebase does this.

You basically need a table that contains booleans that get reset whenever a device goes offline and is no longer reachable.

Add distinct() function to the SDK. The ability of displaying unique values of a field will be useful.

I would like to be able to dynamically create and destroy realms from my swift and java mobile apps. I imagine features in my mobile app that would be best served by a “temporary” realm

Passwordless logins are quite commons nowadays. Firebase supports "Login with email link" (https://firebase.google.com/docs/auth/web/email-link-auth). Would be nice to have the same in Realm.

Realm.open() method used in Middle Tier to fetch data would not find the realm and is waiting for data sync to happen from the device. This method can create a new realm if it does not exist which is not applicable in the context of the Middle Tier apps. Requesting an update to have this default realm creation functionality to be made optional based on a supplied optional parameter.

I could really use file upload/download in my application. I'm attempting to build a PWA in Angular and although we could write a whole other, server-side, api-based application to support file upload/download, it would really benefit the team if this was available in the Browser SDK

For backend Realm DB generation and management, please provide a Golang SDK.

Although in the documentation as working, this doesn't work (https://github.com/realm/realm-js/issues/3494) I pretty much built everything on Realm expecting this to work as documented.
It should be noted in the docs that this doesn't actually work. If there is a workaround available would be great to know about it, haven't been able to get it to work yet.

Hello, I am having problems with authentication via Google Authentication Providers.

The system prevents me from saving the backlink as:
chrome-extension://feomclaleplfhikikgnedghpnhozzzhb/index.html

Throws an error: redirect URI must contain scheme of http or https
"chrome-extension://" is the standard URI scheme.

Please add the ability to add a schema backlink for the chrome extension.

I cannot use other Google Authentication Providers because, if you build the application in the ElectronJS + Chrome-Extention configuration, ElectronJS does not support any authentication protocols. The only way out is to log in using the back link.

Regards, Alexander