Developer portfolio submission checklist.

Start with a working public website

Use a public HTTP or HTTPS link that opens without a private deployment login. Check the final destination after redirects, important project links and the experience on a second device.

A repository can provide useful context, but it does not replace the live website field. Include a repository link only when it is relevant and you have permission to share it.

• Open the link in a signed-out browser.
• Try navigation and project links on a phone.
• Check that loading failures leave useful text or a recovery path.

Explain the contribution, not just the frameworks

The description field accepts 40–2000 characters. Explain what the project does, what you built and one or two decisions that distinguish the work. For a team project, name your contribution without presenting the whole project as solely yours.

Use technology tags that reflect the submitted work. A short explanation of a tradeoff is more informative than an unrelated list of popular libraries.

• State the problem or intended audience.
• Identify your contribution and any collaborators.
• Explain a design or implementation decision a reviewer can inspect.

Prepare a screenshot you are allowed to publish

Choose a still PNG, JPG or WebP image up to 2 MB, at least 320 × 180 pixels and no more than 16 megapixels. The Android app compresses the image before upload; the server checks and processes it again.

Prefer a readable landscape screenshot of the actual project. Thumbnails use public URLs. Remove private account details, access tokens and confidential client information before choosing the image.

Make inspection practical

Readable headings, visible focus states and meaningful project links make it easier to explore the portfolio. Try keyboard navigation, a narrow screen and reduced-motion preferences.

These are practical preparation checks, not a promise of a particular community rating. The site’s scoring and editorial recognition are different processes.

Choose the reviewer and keep the result

Use Universal review or select an available admin. Superadmins can review another admin’s pending queue when necessary. Selecting an admin always requires manual review.

After a confirmed submission, use My Work to track it. Android drafts remain on the current device, expire after 24 hours without a meaningful edit and are cleared on sign-out; they do not synchronize to the website.