Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Prepare English and Korean Android store descriptions and screenshots

Open
#122 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
android
Domain
content, mobile

Research direction

Start with the working reader and distribution choice from #77, and confirm prerequisites #81, #84, and #85 are complete. Prepare reviewable English and Korean summaries and reproducible phone screenshots from synthetic public content, documenting source dimensions and current channel requirements; done means the assets are submitted for review without publishing.

Written by the indexing model from the issue text.

Description

android difficulty: beginner documentation enhancement good first issue help wanted localization

Roadmap: #76

Goal

Create reviewable distribution assets based on implemented app behavior.

Acceptance criteria

  • Write concise English and Korean app summaries describing available features.
  • Capture reproducible phone screenshots from synthetic public content, including both documentation projects.
  • Avoid claims about unimplemented offline, account, or mail features.
  • Record screenshot source dimensions and the selected distribution channel's current asset requirements.
  • Submit the text and assets for review without publishing a store listing.

Start: The working reader and distribution choice from #77. Store access is not needed to prepare the assets.

Prerequisites: #81, #84, #85.

Dominant language
Go
Stars
1
Forks
7
Avg merge
6h 25m
Merged PRs (30d)
18

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavefnd/wave-platform

All issues in wavefnd/wave-platform

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.