IzzyOnDroid first makes sense to me. I'd write the store metadata once in the fastlane layout (fastlane/metadata/android/en-US/ with short_description.txt, full_description.txt and images/phoneScreenshots/). F-Droid reads the same structure from your repo, so the work carries over if you apply there later, and the descriptions can be reused for a Play listing. For the screenshots, capture them from the signed release build with a seeded state, like a sample chat, an agent run and the voice screen, rather than an empty first launch. And because entering the OpenRouter key is the step that loses people, a screenshot of that screen showing the success state is worth including too.
DemoVexa
IzzyOnDroid first makes sense to me. I'd write the store metadata once in the fastlane layout (fastlane/metadata/android/en-US/ with short_description.txt, full_description.txt and images/phoneScreenshots/). F-Droid reads the same structure from your repo, so the work carries over if you apply there later, and the descriptions can be reused for a Play listing. For the screenshots, capture them from the signed release build with a seeded state, like a sample chat, an agent run and the voice screen, rather than an empty first launch. And because entering the OpenRouter key is the step that loses people, a screenshot of that screen showing the success state is worth including too.