I Built ThemeScope to Make Shopify Store Research Easier
Hi everyone! 👋
I'm Naeem, a Shopify developer, and I'd like to share a project I've been working on called ThemeScope.
While building Shopify stores, I often wanted to know which theme or apps successful stores were using. Existing tools sometimes returned incomplete results, didn't recognize custom themes, or required unnecessary signups.
That frustration led me to build ThemeScope.
The goal is simple: make Shopify store research fast, accurate, and free.
Current features include:
Detect Shopify themes
Identify custom and official themes
Discover installed Shopify apps
Identify fonts and store technologies
Recognize when a website isn't running on Shopify
Building ThemeScope has taught me a lot about web technologies, pattern detection, and creating tools for the Shopify ecosystem. There's still plenty to improve, and I'm continuing to add new features based on user feedback.
If you're a Shopify developer, agency, or store owner, I'd really appreciate your thoughts. What features would make a tool like this more useful for your workflow?
You can try it here:
https://getthemescope.com
Thanks for reading, and I'm looking forward to learning from the Indie Hackers community!
One thing I'm curious about: where do you think the boundary is between "research" and "decision-making"?
Knowing which themes and apps a store uses is valuable, but I'm interested in what you believe users still need to figure out after ThemeScope gives them that information.
That's a great question. We see ThemeScope as a research and discovery tool rather than a decision-making tool.
Our goal is to surface accurate, actionable data—such as the store's theme, apps, fonts, and technology stack—so users can understand how a store is built. The decision-making still comes from the user's own expertise, goals, and context.
For example, just because a competitor uses a particular app or theme doesn't automatically mean it's the right choice for another store. Users still need to evaluate factors like budget, performance, compatibility, scalability, design requirements, and business objectives before deciding what to implement.
That said, we'd love to bridge that gap further by providing more context and comparison tools—such as side-by-side store comparisons, historical changes, and exportable reports—to help users make more informed decisions while leaving the final judgment in their hands.
Appreciate the context.
Would be interesting to continue the conversation as you explore how users turn the data into decisions.
What's the best email to reach you on?