The Problem We Were Actually Solving
At the time, our team was working on a digital marketplace for creators to sell their products online. We had successfully onboarded users from the US, EU, and Japan, but the Nigerian user's phone call highlighted the glaring gap in our accessibility. We initially thought it was a technical issue with our payment gateway integrations, but as we delved deeper, we realized that it was a systemic problem. Creators from countries like Pakistan, Ghana, and Bangladesh faced significant hurdles in accessing our platform store due to regional payment restrictions.
What We Tried First (And Why It Failed)
We started by trying to work with our existing payment gateway providers, asking them to onboard users from these restricted countries. Unfortunately, these providers were not willing to accommodate our clients, citing regulatory complexities and risk aversion. We also experimented with alternative payment methods like mobile wallets or cryptocurrencies, but these solutions came with their own set of issues, such as high transaction fees and limited adoption. Our attempts to "patch" the problem only seemed to paper over the cracks, and we were stuck.
The Architecture Decision
That's when I decided to take a step back and reassess our architecture. As a systems engineer, I knew that the issue was not with our platform store per se, but with the underlying systems that governed its accessibility. I proposed a radical shift: abandoning the global platform store for a more decentralized, country-specific approach. We would create regional storefronts, each with its own payment gateway integrations tailored to the local market. This decision would require significant changes to our codebase, infrastructure, and even our business model. However, it seemed like the only way to truly "rust" the digital borders that restricted our creators.
What The Numbers Said After
After implementing the new architecture, we saw a significant increase in creator onboarding rates from restricted countries. In the first month, we saw a 300% increase in new users from Nigeria and a 200% increase from Pakistan. Our transaction volume also increased by 50%, with a corresponding decrease in payment gateway failure rates. The data was clear: our creators were now able to access our platform store, and we were finally reaching the global market we had always talked about.
What I Would Do Differently
In hindsight, I would have pushed for this architecture decision earlier on. Instead of trying to "band-aid" the problem, I would have advocated for a more fundamental shift in our approach. It's easy to get caught up in the excitement of launching a global platform store, but it's essential to remember that accessibility is not just a technical issue; it's also a business decision. As engineers, we need to be willing to take a step back and reassess our assumptions, especially when working with creators from diverse backgrounds. By doing so, we can create systems that truly serve the needs of our users, not just those of our privileged perspectives.
Top comments (0)