Why an Indie Dev Merged a Game Discovery Tool into Another
This article explains why one indie developer decided to fold a standalone game discovery tool into another, larger tool. The short answer is that the developer realized the two tools served overlapping audiences, and merging them reduced maintenance costs, improved the user experience, and allowed for a single, more powerful feature set. Below, we explore the background, the reasoning, the practical steps, and the lessons learned from this kind of consolidation.
Background: The Two Tools and Their Audiences
The indie developer had created two separate web-based tools. The first, a game discovery tool, helped users find new games based on genre, platform, and user ratings. The second, a game library manager, let users track the games they owned, their playtime, and their wishlist. Both tools were free, browser-based, and shared a similar minimalist design. They attracted a small but loyal user base, with some users actively using both tools side by side.
Over time, the developer noticed that many users would copy their library from the manager into the discovery tool to get recommendations, or they would manually check their wishlist against the discovery tool’s search results. This duplication was inefficient and confusing. The developer also had to maintain two separate codebases, two sets of user accounts, and two sets of bug reports. The decision to merge was not sudden but came from analyzing user feedback and usage patterns over several months.
Why Merge? The Core Reasons
There were three primary reasons for the consolidation:
- Reduced maintenance burden: Maintaining two tools meant fixing bugs, updating dependencies, and adding features twice. A single tool halves that workload.
- Better user experience: Users no longer had to switch between two tabs or manually transfer data. A unified interface allowed for seamless workflows, such as marking a game as owned and immediately seeing similar recommendations.
- Data synergy: By combining the library data with the discovery algorithm, the tool could offer personalized recommendations based on what the user actually owned and played, rather than just generic genre matches.
These reasons are common in software consolidation, but for an indie developer with limited time, the maintenance burden was often the deciding factor. The developer estimated that merging saved roughly 10 hours per week that had been spent on duplicate upkeep.
How the Merger Was Executed
The developer took a phased approach to avoid alienating existing users. First, they added a data export feature to the discovery tool so users could save their preferences. Then, they built an import function into the library manager that could read those exported files. After a few weeks of beta testing, they redirected the discovery tool’s URL to the library manager and added a prominent banner explaining the change.
One of the trickiest parts was preserving user accounts. The two tools had separate login systems, so the developer wrote a migration script that matched users by email address. If a user had accounts on both tools, their data was merged; if not, they were prompted to create a new account on the merged tool. The entire migration took about three days of work, including testing.
Common Problems During the Transition
Not everything went smoothly. The most common issues were:
- Lost data: Some users who had never exported their discovery preferences lost them because they didn’t read the banner. The developer mitigated this by keeping a read-only archive of the old tool online for six months.
- Confusion about new features: Users who only used the discovery tool were suddenly faced with library management features they didn’t need. The developer added a simple toggle to hide those sections.
- Performance dips: The merged tool initially loaded slower because it was fetching both library and discovery data on every page. The developer optimized the database queries and added caching, which resolved the issue within a week.
These problems are typical when merging two products, and the developer’s transparent communication on their blog helped retain most of the user base.
Comparing Before and After
Before the merge, users had to use two separate tools with different URLs, logins, and visual styles. After the merge, they had a single tool with a unified interface. The discovery algorithm improved because it could now use the library data as input. For example, a user who owned 100 strategy games would get recommendations for similar strategy games they didn’t own, rather than a generic list of popular titles.
The developer also reported that user engagement increased after the merge. The average session length grew from 4 minutes to 7 minutes, and the number of games added to wishlists per session doubled. While these metrics are specific to this case, they illustrate the potential benefits of consolidation.
Costs and Trade-offs
Merging wasn’t free. The developer spent about two weeks of full-time work on the migration, which is significant for an indie developer. There was also a risk of losing users who preferred the simplicity of the original discovery tool. Some users complained that the merged tool felt “bloated” with features they didn’t need.
To address this, the developer added a “simple mode” that hid all library management features, leaving only the discovery search. This compromise satisfied most users. The ongoing costs after the merge were lower, but the initial investment was a real barrier. For other developers considering a similar merge, it’s important to weigh the upfront time against the long-term savings.
Alternatives to a Full Merger
Merging is not the only option. The developer could have kept both tools separate but added a shared login and a data-sync feature. This would have reduced the maintenance burden slightly without forcing users to learn a new interface. Another alternative was to build a plugin or extension that connected the two tools, but that would have required even more work.
In this case, a full merger was the right choice because the two tools were so closely related. However, if the tools had served completely different purposes (e.g., one for games, one for movies), a shared backend with separate frontends might have been better. The key is to evaluate the overlap in audience and functionality before deciding.
Frequently Asked Questions
Will my data from the old tool still work?
Yes, if you exported your data before the old tool was taken offline. The developer provided an export button in the discovery tool for several weeks before the merger. If you didn’t export, your data may be lost, but the developer kept a read-only archive for six months that allowed users to manually copy their data.
Is the merged tool still free?
Yes, the merged tool remains free to use. The developer funded the project through donations and optional premium features, such as advanced analytics, but the core discovery and library management functions are free for everyone.
Can I still use just the discovery feature without the library manager?
Yes, there is a “simple mode” that hides all library management features. You can use the tool as a pure discovery engine, and your library data will simply remain unused in the background until you decide to use it.
Why didn’t the developer just build a new tool from scratch?
Building from scratch would have taken longer and risked losing the existing user base. Merging allowed the developer to reuse the code and data from both tools, preserving the features that users already liked. It also meant that users didn’t have to migrate to a completely unfamiliar interface.
What should other indie developers learn from this?
The main lesson is to listen to your users. The developer noticed that many users were manually connecting the two tools, which was a strong signal that they should be integrated. Also, plan the migration carefully: provide export options, communicate clearly, and keep an archive for a while. Finally, be prepared to compromise by adding features like “simple mode” to satisfy users who preferred the old, simpler tool.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.