The story behind DownGo · Bangladesh
How DownGo Was Built
From a personal search for a download manager to learning, testing, and publishing a Windows app—this is the independent developer’s story behind DownGo.
My name is Nurnobi Islam, and I am from Gazipur, Bangladesh. I am currently a first-year Chemistry student at the National University of Bangladesh. Alongside my academic studies, I have a strong passion for software development and technology.
I am writing to share my journey of building Downgo – Fast Download Manager, a Windows application that I independently developed using Python and published on the Microsoft Store under the Rafix Technologies brand.
By Nurnobi Islam · Rafix Technologies ·
The problem that inspired me
My journey began with a familiar problem. I regularly used Internet Download Manager (IDM) to download files, images, videos, and other content on my Windows computer. I wanted a more affordable option that I could keep using without a paid subscription.
At one point, I used an unofficial cracked copy of IDM. Afterwards, I noticed unusual problems with my computer, including slow performance, missing files, and unexpected Gmail login notifications. Eventually, Windows became corrupted. I cannot say for certain that the software caused all of these problems, but the experience made me think seriously about software security and getting apps from trustworthy sources.
I began looking for a free download manager for Windows. I also wanted to build something of my own: a modern app with a clean interface, a capable download engine, and optional Pro features. That idea became DownGo.
Starting from scratch with Python
On June 22, 2026, I began developing DownGo using Python. I started with a basic download engine, then built the app’s interface. Real-world testing quickly showed me that many downloads did not complete successfully.
Rather than abandon the project, I studied how download engines work. I used documentation, experiments, and AI chat tools to learn about connection management and parallel downloads. My early results were far from perfect: in one round of tests, only one of five files downloaded successfully.
Those failures taught me that a download manager is much more than a user interface and an Add button.
Learning, testing, and improving the download engine
I researched download-engine design and tested different approaches. I implemented parallel downloading, first using four connections for supported downloads. I kept refining the engine, fixing errors, and improving compatibility with different sources.
Later versions expanded the available connection limits, added internet speed monitoring, and introduced dark and light themes. I built successive Windows versions, moving from early prototypes toward a more complete application.
Each iteration meant testing, finding bugs, making changes, and testing again. My goal was not only to make DownGo look modern, but to make its core download controls useful in everyday work.
From version 1.0 to a more complete product
The project evolved through versions including 1.0.0, 2.0.14, 3.0.1, and 4.0.7. As it matured, I continued improving the interface and download engine. I also developed optional Pro features, including support for more connections on eligible downloads, and a licensing system for advanced tools.
What began as a personal attempt to find a download manager I could afford gradually became a full Windows software project.
The challenge of publishing without a budget
Once I felt ready to share DownGo, I wanted it to reach people beyond my own computer. Publishing software also brought a financial challenge: some distribution platforms required developer-account fees I could not afford.
I first published version 4.0.7 on GitHub and Product Hunt. After about a month without meaningful downloads, I realized that simply making software available online does not guarantee people will discover it. I continued searching and found an opportunity to apply to the Microsoft Store through its free Partner Program.
The Partner Center account is registered to my father, who helped me complete account verification. I am the developer behind DownGo.
Four rejections before the breakthrough
Getting DownGo into the Microsoft Store took persistence. My first submission, version 4.0.0, was rejected after review because of bugs and other issues. I fixed the reported problems, improved the app, and submitted new builds. DownGo was rejected four times in total.
Each rejection meant understanding the feedback, correcting issues, testing again, and preparing another submission. I treated the process as a chance to improve the product. Eventually, Microsoft approved DownGo, and version 4.0.7 was published in the Microsoft Store.
That approval represented more than a successful submission. It reflected repeated experimentation, learning, and persistence.
Where DownGo stands today
As of October 11, 2026, DownGo is at version 4.0.27 and is published through the Microsoft Store under the Rafix Technologies brand. It is built with Python and is intended to give Windows users a modern download-management experience.
Development has included parallel downloads, queue and resume improvements, internet speed monitoring, theme options, and an optional Pro licensing model. I continue working to make the application more reliable and useful.
Product: DownGo – Fast Download Manager
Developer brand: Rafix Technologies
Developer location: Bangladesh
Official website: downgo.online
My next goal: reaching users around the world
Building DownGo was the first challenge. Helping people discover it is the next one. With a limited marketing budget, I am exploring organic growth, software communities, search visibility, product reviews, and technology publications.
This journey has taught me that software development involves much more than writing code. It takes patience, research, testing, problem-solving, and the willingness to continue when things do not work the first time.
DownGo started with a personal frustration. Today, it is a published Windows application from Bangladesh. I hope to keep improving it with feedback from the people who use it.