Its already being build out that way, since I know that we will be changing things in the future. Most of the data will be coming from the server, but there are a few things that need to be persisted. At some point we are going to allow a fully offline mode which is where we will be adding databases.

@cuebyte has left the channel

for people that wants to use Android Studio 2.3, they released an update yesterday on the stable channel : https://plugins.jetbrains.com/plugin/6954

this version works (and it works with kotlin 1.0.6-eap in the build.gradle)

Anyone else getting the warning that

onDestroyView should call super.onDestroyView

even though you are calling super?

Yup known bug

Will be fixed in 1.0.6

Cool, thanks

@ccrowe Has your company considered using Firebase?

For FCM, remote config and dynamic links yes, for databases and crash reporting, no. We generally roll our own postgresql servers, or use whatever the client has setup.

is someone here published an app created with anko?

I've published a couple of apps with Anko

@simon.vergauwen can you post me the link of the app?

I've had 3 apps in production. 3 aren't on the the store anymore due to being temporarily promotional apps.

I'm currently working on a large project where we also use Anko, it's due to be released in March. Ping me then again for a link ;p

Why? If I may ask? What did you expect to see different in an app?

@simon.vergauwen the performance. I only want to test 😄

I don't use Anko for the performance boost (it's nice but depends on your minSdk, user base and how advanced you layouts are) but I use it for the extremely clean and good patterns you can write with Anko.

Runtime layout building is awesome.

I tried to use anko but the preview plugin was broken

Is anyone having trouble getting the

matches()

method of the hamcrest library to work?

For some reason that one method is just gone.

Error:(10, 14) error: DaggerDataBindingComponent is not abstract and does not override abstract method getImageBindingAdapters() in DataBindingComponent

after change from Kotlin 1.0.5-2 to 1.0.6-eap-112 anyone have similar issue?

@User uploaded a file: DataBindingComponent

looks like kapt3 issue so I moved to #kapt

I can’t find a definitive answer, and can’t get it to work myself – did lint-via-command line/gradle get implemented? Is there a YouTrack issue I can follow?

Hi. I'm working against a REST Api where the response has two objects (a, b )of interest can be any combination of

List<SomeObject>, null, SomeObject

I already handled the List<SomeObject> and null responses. But the problem is the JSON response always has the same name, but may be an array or an object.

eg it can be Z  = List<SomeObject> or Z = SomeObject

Can I solve this in some nice way?

Write a JSON adapter which peeks at the first character and sees if it's the beginning of an array or the beginning of an object

If it's an object then wrap it as a single-item list

Fair enough. Thanks for input