PhilippC / PhilippC/keepass2android

[FEAT] KeePass2Android Keyboard should search by URL in Browser instead of Browser API Key

Open
#3,287 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

The KeePass2Android keyboard should be configured so that when searching from a browser such as DuckDuckGo or Firefox, the current URI is used as the search parameter instead of the AppID, such as "com.duckduckgo.mobile.android"—for example, Paypal.de
Screenshot_20260815_191713_Keepass2Android.png

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by tracing how the KeePass2Android keyboard identifies browser requests and currently derives the AppID search parameter. Reproduce the behavior in DuckDuckGo or Firefox and compare it with the requested URI-based lookup, such as Paypal.de. Done means browser searches use the current URI while other app lookups retain their existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.