Hi, this is native so it will perform exactly as native code does. Yes the database would have a different implementation for iOS & for Android.
Native interfaces don't allow passing arbitrary objects since the native iOS VM (and a few of the other VM's) would be hard to use with objects. You can pass a JSON string into the native interface. Since the iOS native API won't be able to use a Java level JSON object anyway that makes sense. You will get a NSString (which is the native iOS String type) in the iOS side and you can work with that. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/6ad8f3d9-f746-47bd-aaf9-08179705d146%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
