Post by Charlie Pyper (@charlie_pyper)
Stream of consciousness on the software build philosophy at @lekeelekee
The default approach is to build our own tooling rather than reach for third-party SaaS. A few reasons behind that:
1. The platform is positioned on African digital sovereignty, so running it on the same foreign platforms its offering an alternative to would undercut the whole point. Operational choices have to match the mission.
2. African connectivity isnt Western connectivity. Off the shelf tools are tuned for high-bandwidth markets. Building our own means we can optimise for low-data, intermittent networks, which is the reality the users often face.
3. The tooling we build today is a potential for our community in the future. As LekeeLekee evolves into a super-app with creators and mini-apps, internal tools can become external offerings.
4. Control over the roadmap. We fix things ourselves, ship at our own pace, and dont sit waiting for our suppliers / vendors to update.
There is a pragmatism behind this we are not building from scratch, where it doesnt make sense. We simply do not have the infrastructure and scale of the huge western tech companies.
More work than buying SaaS? Yes. The right work for whats being built? I think so.
0 likes · 0 comments · 0 shares
Comments
You guys are actually walking the talk. Thereby building your own tools to ensure that the platform’s dynamics is as African as its user base.
We align with your vision and goals💥
Well done @charlie_pyper and the entire team
It also positions @lekeelekee to create tools that can later become revenue products for the ecosystem
Harder now but more valuable long term. Kudos @charlie_pyper and all the Team.
respect.
Keep going! 🔥
Building what is customized for and from Africa to the world is a critical move for the African market. When you control the roadmap, you control the future. Should the foreign vendors change the API,...
That said, the balance you mention...