How I Built Scann Without a Computer!!!
How I Built Scann Without a Computer!!!
No laptop. No desktop. Just an Android phone, a few tools, and a lot of trial and error.
Building software is something I’ve always wanted to do. I’ve always been interested in technology, applications, and the idea of creating something that people can actually use.
But there’s one small problem with my development journey.
I don’t own a personal computer or laptop.
Yes, I’m serious.
Most of the development work I do happens on my Android phone. I don’t have a dedicated workstation, a personal VPS, or an expensive development setup. I mostly rely on free tools and whatever resources I can get my hands on.
And somehow, I managed to build an Android application, publish it on Google Play, get hundreds of downloads from different countries, and even start generating a little revenue from it.
The application is called Scann.
This isn’t a story about building some revolutionary piece of software. It’s about how I managed to take a relatively simple idea and turn it into an actual Android application without owning a computer.
So, let’s start from the beginning.
My Development Setup
My primary development environment is an Android phone.
I use Termux for most of my development-related tasks. It’s basically where I manage my projects, work with Git, execute commands, and handle different things that would normally be done through a terminal on a computer.
I also use GitHub extensively for repository management and version control.
One of the most important parts of my setup is GitHub Actions. Since I don’t have a computer to build Android applications locally, I use GitHub’s CI/CD infrastructure to handle the build process.
My general workflow looks something like this:
- Claude: AI assistance, code generation, debugging, and understanding implementations.
- Termux: My primary development environment.
- GitHub: Source code, version control, and repository management.
- GitHub Actions: Automated dependency installation and Android builds.
- Google Play Console: Testing, release management, and publishing.
That’s pretty much my development environment.
Nothing particularly fancy, right?
But it gets the job done.
I Didn’t Know Much About Android Development
Before starting Scann, I didn’t have much practical experience with native Android development.
Kotlin and Flutter weren’t technologies I could confidently say I knew how to work with.
I wasn’t an experienced Android developer trying to build another application. I was learning things while building them.
I started using Claude and other AI tools to help me understand the code, implement features, fix bugs, and work through problems.
And that’s where things get interesting.
AI Won’t Do Everything For You
I want to talk about AI-assisted development because I think there’s a misunderstanding about it.
A lot of people see AI generating an entire application and assume that building software has become incredibly easy.
You just describe what you want, AI writes the code, and apparently you’re done.
Well, not exactly.
At least, that’s not how it worked for me.
I used Claude extensively while developing Scann. It helped me write code, understand implementations, troubleshoot problems, and work on features that I couldn’t confidently implement myself.
But here’s the thing: AI doesn’t understand your entire project perfectly all the time.
Sometimes it generates code that looks correct but doesn’t fit your existing project context. Sometimes you ask it to fix one issue, and suddenly something completely unrelated stops working.
And debugging AI-generated code can sometimes be more exhausting than writing some of it yourself.
You still have to review the code, understand what’s happening, test the implementation, identify mistakes, and make sure everything actually works.
AI can write the code, but eventually, you’re responsible for the result.
My personal opinion is that AI should be used as a tool, not as a replacement for your ability to think.
I find AI particularly useful for complicated or repetitive tasks that would otherwise consume a significant amount of time.
But blindly generating an entire application without understanding anything about it? I honestly don’t recommend that.
Sometimes, using AI effectively requires even more thinking than you might expect.
The Actual Development Workflow
My development workflow was a little different from what most Android developers are probably used to.
I worked on the project through Termux, used Claude to assist with development, and pushed everything to GitHub.
Whenever I needed a new Android build, GitHub Actions handled the process.
The workflow was relatively straightforward:
- Work on the application using Claude and Termux.
- Push the changes to GitHub.
- GitHub Actions starts the workflow.
- Required dependencies are installed.
- The Android App Bundle (AAB) gets generated.
- Download the generated artifact.
- Install and test the application on my phone.
If something breaks, I go back to Claude, explain the issue, review the suggested changes, and try again.
Sometimes I fix things manually. Sometimes I need AI assistance.
Then the entire process repeats.
Code, build, test, debug, and build again.
Honestly, I’m really grateful that GitHub provides GitHub Actions. Without it, managing Android builds from my current setup would have been considerably more difficult.
Microsoft deserves some credit for making this kind of infrastructure available to developers.
Why I Wanted to Publish an Actual App
I didn’t just want to experiment with code forever.
I wanted to build something that people could actually download and use.
That’s when I started working on Scann, a QR code and barcode scanner.
It wasn’t a revolutionary idea. There were already thousands of QR scanner applications available on Google Play.
I wasn’t trying to compete with some massive software company.
I simply wanted to build an actual Android application, experience the development process, and see whether I could take something from an idea to a real product.
And eventually, I did.
My First Google Play Console Experience
This was probably one of the most exciting parts of the entire experience.
Before Scann, I didn’t really know how Google Play Console worked. I had never gone through the complete process of publishing an Android application.
Registering the application, preparing the store listing, uploading the AAB, configuring testing tracks, and going through Google’s review process were all new experiences for me.
I still remember the first time I generated an AAB through GitHub Actions and uploaded it to Play Console.
It felt different.
You spend hours working on something, fixing problems, testing it repeatedly, and eventually you have an actual application package ready to be submitted to Google Play.
Then comes testing.
The Tester Problem
For my release, I had to go through the required testing process, including arranging around 12 testers for closed testing.
And honestly, managing testers as an individual developer can be surprisingly difficult.
If you have an established company or a team, finding people to test an application might not be a huge problem.
But when you’re an individual developer, it’s a completely different story.
You ask friends and family members to participate, and sometimes even something as simple as providing an email address becomes a whole discussion.
I understand that people have privacy concerns. That’s reasonable.
But sometimes you’re literally just trying to add someone to a Google Play testing track. You’re not asking for their entire personal information.
Anyway, after completing the required testing period, I was finally able to apply for production access.
Finally, Production!
The entire process took roughly 14 days before I reached production.
And then, Scann was officially available on Google Play.
I genuinely think publishing your first application is an experience every aspiring Android or iOS developer should have.
There’s something special about seeing your own application on the Play Store.
It’s no longer just a project sitting in your repository. It’s something other people can install, use, and interact with.
You also learn that application development isn’t just about writing code.
There’s testing, distribution, release management, versioning, maintenance, and eventually dealing with actual users.
You understand a lot more once your application is out in the real world.
And for me, that was a completely different experience.
I had finally published something of my own.
Now came the interesting part.
Would anyone actually download it?
I Wasn’t Expecting Anyone to Download It
After publishing Scann, I honestly didn’t expect much.
I thought it was just another QR scanner. There were already thousands of similar applications available on the Play Store.
I assumed a few people might download it, try it, and probably uninstall it.
I continued working on updates, reviewing the code, fixing small bugs, and maintaining the application.
I tried to push updates every two or three days whenever I had something worth changing. I also tried to maintain proper versioning through GitHub and keep track of the changes.
Then, after roughly two months, I opened Google Play Console to check how the application was doing.
And I was genuinely surprised.
The dashboard showed around 400 first-time installs.
Four hundred.
Wait, what?
I had always seen the Play Store displaying 100+ downloads, so I assumed the application had probably received somewhere around that number.
I didn’t realize the actual number was considerably higher.
Then I started looking at the country statistics.
India had the most downloads. There were also users from the Philippines, France, the United States, the United Kingdom, Nigeria, Pakistan, and several other countries.
Hold on.
People from all these countries were actually downloading an application that I had built using my Android phone?
That was a genuinely surreal feeling.
Think about it for a second. If I went to a field somewhere around Mirpur and gathered 400 people together, that would already look like a pretty large crowd.
And here I was, looking at hundreds of people who had independently downloaded my application from different parts of the world.
I know the number isn’t huge in the context of the Play Store. But seeing it for the first time made me realize something.
Even a small application can reach people you’ve never met and probably never will.
To everyone who downloaded or used Scann, thank you. Seriously.
Whether you installed it from India, the UK, the US, France, Nigeria, Pakistan, or anywhere else, I genuinely appreciate it.
It Wasn’t Just About Writing Code
I want to be honest about something.
Scann is, in many ways, a vibe-coded application.
I’m not going to pretend that I independently wrote every line of Kotlin or that I have some extraordinary Android engineering experience.
I don’t.
But I did spend a considerable amount of time working on it.
I stayed up late trying to get things working. I repeatedly tested builds, reviewed implementations, tried different UI ideas, fixed problems, and learned how the publishing process worked.
I put time into the project.
And I think that matters too.
I spent time thinking about how the application should look, how certain features should behave, and what I could improve in the next update.
I might not have written all the underlying code myself, but I was involved in the process of turning an idea into something people could actually install and use.
I also had to learn how to work with AI, how to explain problems properly, and how to figure out when something wasn’t working as expected.
That’s an experience I genuinely value.
A Little Monetization Experiment
For the first couple of months, Scann was completely free to use without advertisements.
Eventually, I started thinking about monetization.
There is a practical reason behind that decision.
My financial situation isn’t particularly comfortable, and I’ve also been dealing with some uncertainty regarding my studies.
At some point, I realized that building free applications forever wasn’t going to solve any of those problems.
I needed to at least try to generate something from the things I was building.
So I decided to integrate Google AdMob into Scann.
I know advertisements aren’t necessarily the most beautiful addition to an application. They can affect the overall user experience, and I had previously preferred keeping the application completely ad-free.
But sometimes you have to make practical decisions.
I enabled advertisements just three days before writing this article. So it’s still very early to judge how well the monetization will perform.
Initially, I didn’t expect much.
Then I opened AdMob one morning after waking up.
And there it was.
$1.68.
My first reaction was basically:
Wait, what? How did I even make a dollar?
It might sound funny, but seeing that number for the first time was surprisingly exciting.
It’s not a lot of money. I know that.
But it was the first time I saw an actual revenue figure generated by an application I had built and published.
Then I started checking the numbers again.
The downloads were increasing, and the revenue was showing up.
I was genuinely surprised.
For now, I’ll let it run for a month or so and see what happens.
Let’s see how it goes. Allah knows best.
What About TheKami?
Scann is also part of a bigger picture.
I’m involved in building TheKami, and I never wanted it to become just another GitHub organization with a nice name and an empty repository list.
I don’t have years of professional experience. I haven’t worked at a major software company, and I don’t have an extensive entrepreneurial background.
But I believe starting something means actually doing something with it.
You make a plan, start building, release something, receive feedback, improve it, and continue.
Then you do it again.
A startup shouldn’t be something you create once and leave sitting around.
There will be updates, new projects, experiments, mistakes, and probably a lot of things that won’t work.
That’s normal.
Ruhan, who is also part of TheKami, has his own computer and contributes to projects as well. However, he also has personal responsibilities and work commitments. We can’t always depend on one person to handle everything.
So I try to keep building from my side, using whatever resources I have available.
We have several ideas for the future, including more software, applications, open-source projects, and possibly even games.
We’re still figuring things out, but we want to keep moving.
What’s Next?
I don’t know exactly how far I can take this.
I don’t know whether Scann will reach 1,000 downloads, 10,000 downloads, or something beyond that.
I don’t know how much revenue it will generate over the next few months.
And I definitely don’t have everything figured out.
But I have learned quite a lot from this experience.
I now have a much better understanding of Android application development, GitHub Actions, automated builds, Google Play Console, testing tracks, production releases, version management, and application monetization.
Most importantly, I now know what it feels like to publish something of my own and see people actually using it.
All of this happened without owning a personal computer.
I’m not saying that you don’t need a computer to become a developer. Having a proper development machine would obviously make many things easier.
But I also don’t think you should always wait until you have the perfect setup to start learning or building something.
Sometimes you just have to work with what you have.
A phone, an idea, some free tools, a little patience, and a lot of trial and error.
That’s pretty much how Scann happened.
And this is probably just the beginning.
A Small Thank You
If you’ve read this entire article, thank you for spending your time here.
I know this wasn’t some extraordinary technical achievement, but it was an important personal experience for me, and I wanted to document it somewhere.
If you want to try Scann, you can find it on Google Play. You can also check out my portfolio, LinkedIn profile, and TheKami website.
We also work on open-source projects from time to time. If you find something useful and want to support what we’re building, contributions and donations would genuinely mean a lot to our small team.
Find Me Online
If you want to connect with me or check out what I’m working on:
- Scann: Google Play Store
- Facebook: shkshoudo
- LinkedIn: asikrshoudo
- GitHub: asikrshoudo
- TheKami: thekami.tech
- TheKami GitHub: thekami-co
- Email: info@thekami.tech
Thanks for giving Scann a try. Whether you installed it yesterday or have been using it for a while, I genuinely appreciate it.