Get a standard TFLite Android demo application coded against either the C API or JNI running.

[benvanik]

They have an image classifier demo / info known to work with the GPU models that we will be trying.

It uses their JNI wrapper that we can rip up to start as they include delegates and stuff whereas we just want something that uses the C API.

I think for the sprint we can just fork the whole demo + it's config into experimental/ (changing some things of course ;).

Once we can use vcpkg to build an AAR it'll be much easier to get demos like this stood up, but until then we can just hack the build until it works.

[ScottTodd]

How do we feel about putting Android app code in IREE's experimental/ vs creating a dedicated iree-samples repository? The Android file paths can get pretty long :P

[benvanik]

I think ideally long-term samples live in their own repo so they can be versioned and don't turn into a monorepo - so google/iree-samples-android/ would have all the copies of gradle jars and icons and xml files and source model files and crap, not our main repo. Short term a single demo could live in google/iree/experimental/, but I'd almost prefer saying that it lives in scotttodd/iree-android-tflite-demo-mumble/ and is something we link to until we want to formalize that. Be agile and such. Even short term we probably shouldn't be in the business of having tflite-based android demos in our repo, and experimental/ would just be for collaboration if it was helpful.

[ScottTodd]

Agreed. cc @not-jenni + @KoolJBlack

[antiagainst]

I think someday we should have an IREE GitHub organization for hosting various projects. ;-P

[ScottTodd]

Done at https://github.com/not-jenni/iree-android-tflite-demo, will move to https://github.com/google/iree-samples soon.