A tool I use, with its original author credited
RespectASO is an open-source App Store keyword research tool built by Respectlytics. The local workspace and self-hosted service make it part of my app-growth tooling; they do not make the original project a Trinx-created product. The repository is licensed under AGPL-3.0. I keep that attribution visible because a useful technical portfolio should distinguish products I build from third-party tools I operate or adapt. Both can be worth writing about, but they are different contributions.
What a keyword result contains
The tool uses the public iTunes Search API for competitor information and builds popularity and difficulty estimates from those signals. It also supports multiple countries, keyword comparisons, history and CSV exports. These features are useful for organising a research pass around a real app. I can inspect the competing apps and compare markets rather than choose words only because they sound attractive. The result gives a shortlist for further validation, not a guarantee that a particular keyword will bring downloads.
Estimates need labels
A popularity score inferred from competitor data is different from a measured search-volume report. Download projections are estimates too. I treat them as research signals and compare them with the app’s actual performance after a change. That keeps a convenient dashboard from becoming false precision. The same discipline applies to SEO work on Rolagzza: useful metadata and clear content can support discovery, but neither establishes rankings or conversions before there is real evidence.
Self-hosting and the next check
The project runs through Docker with a local data volume, and the Hetzner inventory contains a RespectASO web service. The next practical check is to follow one keyword research decision through an actual store metadata experiment. Which term changed, in which market, and what happened afterwards? That produces a useful app-growth story while preserving the limits of the underlying estimates. The original project and documentation remain the right place to start for installation and methodology.
Continue reading
The current portfolio, server-side AI architecture and my development workflow. Browse all projects or follow the newsletter.