Feature Request: Add support for Sabilytics Analytics

[unclebay143]

Hi 👋

First, thank you for building this project.

I recently launched Sabilytics, a web analytics platform, and thought it could be a useful analytics option for users of this project.

If this is something you'd be open to, I'd be happy to contribute and maintain the integration.

No worries if it isn't a direction you'd like to take, I just wanted to start the conversation and hear your thoughts.
https://x.com/unclebigbay143/status/2080563856552727027?s=20

[HalxDocs]

Hey, thanks for opening this and for the kind words on the project 🙏

Before I can say yes or no, I want to understand the actual use case better. Reqit is an API client, not a website/app with end users, so I'm not sure where "analytics" would plug in for us. A few things I'd need clarity on:

• Is this meant for reqit.dev (the marketing site), or something inside the app itself (e.g. usage/telemetry tracking)?
• If it's the latter, that's a harder sell since reqit is positioned as local-first, and I'm cautious about baking in third-party trackers even opt-in ones without a really clear reason and full user control.
• What would the integration actually look like on our end (a script tag, an SDK dependency, config in the app, etc.)?

Happy to keep talking through it, but I'd want to see it solving a real problem for reqit users specifically, not just be an available option for the sake of it. Appreciate you reaching out either way.

[unclebay143]

Thanks for the thoughtful response @HalxDocs, and those are fair questions.

To clarify, I wasn't suggesting analytics inside the Reqit desktop app or collecting telemetry from users. I completely understand and respect Reqit's local-first philosophy.

My suggestion was specifically for reqit.dev (the marketing/docs website), where Sabilytics could help answer questions like:

• Which pages attract the most visitors?
• Where are visitors coming from?
• Which documentation pages lead to downloads?
• How discoverable is Reqit in AI tools and search engines?
• What improvements could increase discoverability over time?

as this metrics can help improve the website experience.

While Sabilytics provides website analytics,

one of the things we're building towards is helping developers understand not just how people use their website, but how people discover it including AI discoverability and search discoverability.

From the integration side, it would simply be the standard Sabilytics tracking snippet (or framework integration if the site uses one). No SDK inside the desktop application, no telemetry, and nothing that changes Reqit's local-first principles.

If website analytics isn't something you're looking to change right now, that's completely understandable. I mainly wanted to offer Sabilytics as another option if you ever decide to revisit your analytics stack.

Thanks again for taking the time to consider it.