Describe the bug

When building Mac apps using Realm, the database files are saved in ~/Application Support/your.app.identifier/someFile

Realm-Studio can't access this location because someone forgot to add showHiddenFiles to the NSOpenPanel sheet. Someone ALSO forgot to add the ability to just drag and drop a Realm database onto the window and/or Dock icon, which would be the best solution.

To Reproduce

Steps to reproduce the behavior:

1. Attempt to open a Realm database in any hidden folder on a Mac.

Expected behavior

The "open file" sheet should show hidden folders, which are the most common location for Realm files during app development.

Screenshots

n/a

Versions:

• OS: macOS 12.5.1
• Studio Version 11.2.1

Additional context

Please invest more time and polish into this app. It's painfully slow and clunky on macOS. And you should REALLY care about that, because if my first exposure to Realm had been through this app, I'd have instantly dismissed Realm as comically slow and therefore useless.

The issues abound:

1. The first-launch forces you to provide an email address. (Because you like filling your list with none@none.com, I guess?)
2. Drag/drop support is missing. You can't even drop a Realm database file onto the Dock icon to open it! That's like Mac 101.
3. Launch times are painfully slow.
4. Once you open a database file of non-trivial size, the entire UI simply disappears for a bit while it loads. "Uh, did it crash?"

Basically, this app is just a terrible, terrible advertisement for a really great database system. Please discard the cross-platform JS nonsense and build a couple awesome, native apps so that Realm's capabilities really shine.

Importantly

Non-native apps always have these sorts of issues and performance problems. (Spotify, Slack—heck, you can drag VSCode's window to resize it and watch the screen tear so badly, you'd think it's 1991 again.) I realize I've harshly critiqued Realm Studio, but that shouldn't be taken as an attack on the people who did this work. The root of the problem is the non-native tech stack, not a lack of effort or skill by the people involved.