The hardest parts are always the ones you don’t see: scaling storage & query times, making interpretation meaningful (like “this bounce rate is unusually high”), and doing all of this in a way that’s GDPR/CCPA friendly.
Why do this? Because I believe analytics doesn’t need to feel creepy. You should be able to learn about your users respectfully — see what’s working, diagnose what’s broken — without handing over control or trust.
I’m building an analytics platform and want to fix real—not hypothetical—pain. Can you walk me through, in as much detail as you’re comfortable sharing, the last time you needed a web analytics answer—what you did step-by-step, the tools involved, constraints that shaped the path, and where it broke?
Indeed, the law might be an issue, but hopefully we will not get to that in the end.
Hello! For some time I am working on a Photos app as alternative to Google Photos, but hosted in EU and with E2E encryption. The development is going good, already have an android app and a web version (it is a solo project, I am the developer and all).My question is, do you think it would be feasible? Is it there enough space to market and sell it?I did it because I wanted an encrypted system,...