Back to Blog
ArticleBuild in Public

Week #2: An Android App for Learners & Portfolio Updates

Finishing the first Android app I've built, some updates to the portfolio and KetaCV, and what I learned from working the DevOps way.

6 min read

This week I worked on improving my personal site and KetaCV in a few areas: the design, the user experience, and some small technical things I'd been putting off for a while.

And the big one: I finished building an Android app I've been working on for some time, and I plan to release it soon. Right now I'm testing it. I decided to use it myself for a week or two before I make the final call on launching.

⚒ What I actually got done this week

  • Design and UX improvements on the portfolio
  • Cleanup and small technical fixes on KetaCV I'd been putting off
  • Finished building the Android app for learners
  • Started testing it myself before launch

🎯 From a mockup to a real product

The project started as a simple idea to design some app screens, just to show them in my portfolio. But the AI tools helped me a lot with the development side, so I decided to turn the idea into a real app people can use.

The app is for learners, whether they study on their own or at school.

Still, I'm thinking of launching it now to get feedback from early users and make it better, so it's in good shape by the start of the next school year. The app also works well for self-learning, and I'm using it myself right now while taking a DevOps course.

🧱 The biggest lesson from a first app

One of the most important things I learned while building this project, my first app, is that feeling like the app is "perfect" while you're building it means nothing.

There are always tiny details you don't notice while designing or coding, but they make a big difference in how the app feels.

📚 Using DevOps ideas on the product

Since I'm learning DevOps right now, I tried to use the same ideas while building the app:

  • Work on small pieces you can test right away
  • Ship in short cycles instead of building everything at once
  • Get fast feedback after each step
  • Catch problems early instead of letting them pile up

The result was clear: fewer surprises at the end, and a steadier pace of work.

🚀 Next week

Making the final call on launching the app, and following the feedback from early users to see what's worth fixing before the next school year.

Enjoyed the article? Share it