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

Open verified website links in the matching Android reader screen

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android

Research direction

Start with prerequisites #82, #84, and #85 and the #82 fixtures; then trace the Android manifest/association configuration and the website's /.well-known/assetlinks.json delivery path. Verify cold-start and running-app routing, anchor preservation, and browser fallback on a test domain/device; leave production package and certificate values for maintainers.

Written by the indexing model from the issue text.

Description

android difficulty: intermediate enhancement help wanted needs testing

Roadmap: #76

Outcome

Implement App Links for the supported public reader URLs.

Done

  • Route trusted documentation, blog, and release links using #82 fixtures.
  • Restore the intended screen on cold start and while the app is already running; preserve document anchors.
  • Define the manifest/association configuration for the package and signing identity chosen by maintainers.
  • Add a testable /.well-known/assetlinks.json delivery path or deployment configuration as appropriate; exclude it from SPA fallback.
  • Verify the association on a test domain/device and show browser fallback for unsupported/unverified destinations.

Do not invent a production package name or certificate fingerprint. Production association is a release gate once maintainers supply those values.
Reference: Verify Android App Links.

Prerequisites: #82, #84, #85.

Dominant language
Go
Stars
1
Forks
7
Avg merge
1h 45m
Merged PRs (30d)
16

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.