Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking: Metadata extration support for both Java and Swift #154

Open
1 of 2 tasks
sseppola opened this issue Sep 1, 2020 · 6 comments
Open
1 of 2 tasks

Tracking: Metadata extration support for both Java and Swift #154

sseppola opened this issue Sep 1, 2020 · 6 comments
Assignees

Comments

@sseppola
Copy link

sseppola commented Sep 1, 2020

I would just like to set up an issue to track when this lib can be used to extract labels from a tflite bundle in both iOS and Android. Current support:

  • Android, Java
  • iOS, Swift

For context:
I'm using Firebase ML to manage custom models for my apps, however managing the labels separately from the model is a pain point. I prefer to solve uniformly in both apps to keep things simple, so I need both java and swift implementations to be ready.

@lu-wang-g
Copy link
Member

The C++ metadata extractor library has been released. We're working on improving the C++ user experience so that it's easy to use when building from source code.

@sseppola
Copy link
Author

Excellent! Thank you for the update.
I'm not in a hurry to have this in place, so I read your comment as a suggestion to wait until the user experience has been improved before integrating the C++ lib. Is that a fair assessment?

@lu-wang-g
Copy link
Member

The improvement will focus on non-bazel experiences, such as using CMake.

BTW, what is the expected workflow for your use case, like which platform (c++/ swift / java), prebuilt binary or built from source code?

@sseppola
Copy link
Author

I'm new to native apps, so I'm not sure what tool is being used under the hood, but I can describe the setup.

I've got a React Native app with custom native integration to TFLite, this all builds with default swift/java compilers as far as I know. My project dependencies have been installed from Pods/Maven/npm, so perhaps there's some step in the bundling that compiles source files in there, but this I'm not aware/certain of.

My build.gradle refers to using BUCK for compile dependencies:

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

Does this answer your question? I'm happy to dig a bit further if you give me some direction

@lu-wang-g
Copy link
Member

Thanks for your explanation! Seems like the missing piece of work for you is the swift API distributed from Cocoapods. I'll make a note when we planning work for the next quarter. Thanks for the feedback!

@sseppola
Copy link
Author

Happy to help! I was starting to expect something more complicated, so I'm looking forward to the cocoapods distribution.

@lu-wang-g lu-wang-g self-assigned this Oct 13, 2020
@Lescurel Lescurel mentioned this issue Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants