4 ms·

I played a bit, but there are 2 things that annoys me: the footprint is really huge, for iOS, Realm.dll has 103 MB, so it means my app will instantly have 100MB

by joe1804 10y ago

I played a bit, but there are 2 things that annoys me: the footprint is really huge, for iOS, Realm.dll has 103 MB, so it means my app will instantly have 100MB more!!!. The second thing(even more important for me) is about the fact that all my storable objects have to be derived from RealmObject, so no POCO support. This is pretty important because I will need to carry Realm dependency everywhere I pass my objects.

brmunk 10y ago
Realm itself only adds less than 1 MB extra in your final app :-) On Xamarin.iOS the Realm static libraries for all the iOS platforms and architectures we support are embedded inside the Realm.dll assembly. During build, Xamarin extracts the static libraries and links the app against them. We should be more explicit about the size implications to avoid that chocking misunderstanding! We will update our FAQ. Re. POCO support: We expect to support that going forward - you can follow the issue here: https://github.com/realm/realm-dotnet/issues/529 https://github.com/realm/realm-dotnet/issues/529. Let us know if you have other questions or concerns! Github issues is a good place to suggest features or ask questions. Thanks!