albertodepaola 31e45e4fae Llama 4 api recipes (#928) 1 tuần trước cách đây
..
app 31e45e4fae Llama 4 api recipes (#928) 1 tuần trước cách đây
gradle a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
.gitignore a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
README.md 0fbd4b27e8 update article to document 2 tuần trước cách đây
build.gradle.kts a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
gradle.properties a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
gradlew a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
gradlew.bat a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây
screenshot.png 31e45e4fae Llama 4 api recipes (#928) 1 tuần trước cách đây
settings.gradle.kts a68f4fd1f7 move folder to e2e-use-cases 1 tháng trước cách đây

README.md

Android Document Summarizer App

This is a sample Android app to demonstrate Llama 4 multimodal and multilingual capabilities. This app allows user to take a picture/screenshot of a document, and then summarize and translate it into any of the supported languages

Quick Start

  1. Open the DocumentSummarizer folder in Android Studio
  2. Update the API_KEY in AppUtils.java
  3. Build the Android Project
  4. Inside the app, tap on settings icon on top right
  5. Configure the Remote URL endpoint (any supported providers that serve Llama 4 models. For example: https://api.together.xyz)
  6. Select the desired model from the drop down list. If you need to add more models, modify ModelUtils.java
  7. Go back to the Main chat window
  8. Press the '+' button on the bottom left and select an image document (or take a picture of one!)
  9. Select the 'globe' button on the bottom left and select your languages
  10. Enter a prompt like "summarize this" and press Enter!

NOTE: This is an example project to demonstrate E2E flow. You should NOT use/store API key directly on client. Exposing your API key in client-side environments allows malicious users to take that key and make requests on your behalf. Requests should always be routed through your own backend server where you can keep your API key secure.

Reporting Issues

If you encountered any bugs or issues following this tutorial please file a bug/issue here on Github).