[GeneralTspoon]

I've used it in a couple of small Android apps. Overall, I wouldn't recommend it (yet) for anything more than toy projects. The sibling post mentioned a few reasons why, but here's are another few:

No inheritance. No nested transactions. No RxJava support (due to threading issues with Realm). Many annoying random errors (for example, get a row then close the DB connection -> You can't use those results after. Although I believe that this is by design because Realm doesn't cache any data - it queries every time it's requested AFAIK).

It's definitely on the way to being an awesome asset, but it's not there yet!

[brmunk]

Yeah we absolutely have a lot of work ahead of us (as mentioned in the post). And the issues you mention are tracked in https://github.com/realm/realm-java/issues. There you can also see that we got a lot more features we want to add than the few you mention :-) We strive to be very transparent about our limitations (http://realm.io/docs/java/0.80.0/#current-limitations) so that they at least don't surprise anyone.

We seriously love to get the feedback so we can prioritize the additional features our users desire the most.

That said, we are very encouraged to see that the current features satisfy a lot of "non-toy" apps as well and that many thousands developers are building new apps every week.

You can see some of them mentioned here: http://realm.io/users/, and at the end of that page is also some unedited interviews with developers.

/Brian from Realm