What it does
SearchMob runs a local metasearch service on Android and combines results from multiple engines. Its project documentation describes per-engine controls, local ranking rules and history disabled by default.
SearchMob runs its Ktor search front end on the Android device’s loopback interface and exposes an OpenSearch endpoint to a browser. It can combine engines and apply local domain rules or filters to the merged results, with optional user-supplied API keys for supported providers.
A foreground service supports background availability and boot startup. History is off by default; enabling it stores an encrypted, removable local history. Update checks are on by default but can be disabled. Queries still reach the selected upstream engine or API, so local operation describes where the front end runs.
Strengths
- History is documented as off by default with optional encrypted local storage.
- Per-engine and local ranking controls are provided.
- A local OpenSearch endpoint supports browser use.
Best for
- Android users comfortable installing and maintaining a local search app