Humna Mustafa

Devlog #2 — MegiLance: Final Build Log 🚀
Okay so… final devlog time.
MegiLance is something I actually built fully by myself — the idea, the design, the backend, the frontend, all of it. And I’m honestly proud of where it reached.
Since my last update, here’s what I shipped:

✨ finished the AI‑based freelancer ranking
🔐 added the full escrow flow for safer payments
💬 built real‑time chat + set up video call support
💸 added multi‑currency + crypto payments
🎨 cleaned up the dashboards and project pages
🔗 connected everything together (Next.js ↔ FastAPI ↔ Turso)

Most of this was me jumping between screens, APIs, and bugs at 3AM — but it was fun in a chaotic Hack Club way. I learned a lot, fixed a lot, broke a lot, and built something that actually works.
MegiLance started as “what if freelancing wasn’t messy?”
Now it’s a working prototype because I sat down and made it myself.
Submitting it here, but not stopping here. 🚀

Devlog #1 – MegiLance 2.0 🚀

17 hours. Straight up. And my brain is buzzing ⚡💻

I started MegiLance 2.0 because I was tired of the usual freelancing chaos — slow payments, sketchy rankings, and no real way to know if a project or a freelancer is legit. I wanted something smart, fair, and fun to use. Something I’d actually want to use myself.

In these first 17 hours, here’s what I did:

Set up frontend + backend (Next.js + FastAPI) and got the basic flow running

Built the Turso database skeleton for users, projects, and payments

Started laying the AI foundation for freelancer ranking 🤖

Hooked up multi-currency + crypto payment system 💰

Designed the first UI components and dashboards 🎨

It’s raw. It’s messy. But it’s alive. Every table, every screen, every API is a piece of something big.

Honestly, this is what building feels like: long hours, tiny wins, big vision. You look at a blank screen, and 17 hours later, you’ve got a skeleton that could actually work in the real world. 🌱

Next up: AI ranking, video calls, smart contract escrow. And I can’t wait to see it all come together 🚀

Devlog #1 – Megicode 💻🚀

Spent 3 hours laying the foundation for Megicode, our software company project. This isn’t just a website — it’s the start of a full-stack, client-ready platform for web, mobile, desktop, and AI-driven apps.

Here’s what I actually did:

Set up Next.js + React frontend and project structure 💻

Built the core pages: About, Services, Projects, Contact

Designed basic UI components and layout 🎨

Connected forms and placeholders for project showcases

Made sure the structure is scalable, ready for real projects and client work

It’s raw, but it’s real work. Every page, component, and folder is planned like a professional software company would do — not just a student project.

Next steps:

Add real project data + portfolio content

Improve UI/UX for accessibility and responsiveness

Start building reusable components for future apps

This is Devlog #1: 3 hours, clear structure, real company workflow. 🌱

Devlog #1 – CampusAxis 🚀🎓

17 hours straight, and CampusAxis is finally taking shape. Honestly, building this feels like turning my own student struggles into something real. I kept losing track of past papers, GPA calculations, and faculty info, so I decided: enough waiting — I’m building my own toolkit.

Here’s what I actually did:

Set up Next.js + React, created the folder structure — everything clean and scalable 💻

Built core pages: GPA Calculator, Past Papers, Faculty Reviews, Lost & Found, Resources

Designed UI and navigation so it actually feels easy to use 🎨

Wired data placeholders and tested features like GPA calculation — it’s accurate, reliable, and ready for real students

Laid the foundation so later I can plug in real past papers, reviews, and lost & found posts

I won’t lie — 17 hours felt long, but seeing a working GPA calculator and past papers section already makes it feel alive. Every click is usable. Every page has a purpose. And this isn’t just for me — it’s for students like me at COMSATS who need a little help staying on top of campus chaos.

Next steps:

Connect real student data for past papers & resources

Add Lost & Found submissions and search

Polish UI/UX for mobile-first, smooth experience

Build community features like forums and study groups

CampusAxis isn’t just a project — it’s my student life, organized and shared 🌱. 17 hours down, hundreds more to go, but it’s already a tool I can be proud of.

Devlog #1 – HostelMate 🏠✨

I spent my first 30 minutes just getting the ball rolling ⏱️

Hostel life is chaotic. Tasks pile up, chores get ignored, and no one knows who’s doing what. I thought: there’s gotta be a better way.

So I started building HostelMate — a mobile-first, gamified system for shared living spaces. It’s all about fairness, points, and making chores actually fun.

In this short session, I:

spun up the web + app structure 💻

designed the logo and visual vibe 🎨

set up the first screens where users can create/join spaces

laid the foundation for tasks, fairness algorithm, and leaderboard

It’s just the beginning — no AI fairness yet, no proof system, no leaderboard logic.
But the skeleton is alive, and it already feels real 🌱

Check the early version here: 🔗 hostel-management-topaz-ten.vercel.app

Starting small, thinking big, building fast 🚀

Devlog #1 – Aesthetic Clinic App

This project didn’t start with code.
It started with discomfort.

I noticed how most aesthetic clinic apps feel cold, confusing, or rushed. You open them and instantly feel lost — too many options, unclear services, and no sense of trust. For something so personal, the experience felt impersonal.

That didn’t sit right with me.

So I decided to build an aesthetic clinic app that feels calm, clear, and human ✨
Something that guides users gently instead of overwhelming them.

Before jumping into features, I slowed down and focused on the foundation. I studied how people choose clinics, mapped user flows, and thought carefully about design decisions that reduce anxiety.

During this phase, I also:

designed the app logo 🎨

set a soft, minimal visual direction

started coding the basic app structure 💻

This work doesn’t always look flashy, but it matters. It’s what turns an idea into something real.

This is Devlog #1.
No big features yet — just intention and a solid start 🌱

More soon 🚀

Devlog #3, I finally had the data.
258+ universities. Verified. Clean. Real.

But then I realized something:
data sitting in Excel = zero value unless the app can actually use it.

So this devlog was about one thing:
turning boring rows into real features.

I started preparing my app to accept real university data instead of dummy content. That meant:

Restructuring screens so they don’t break when real data comes in

Cleaning navigation (no random jumps anymore 😭)

Making sure every screen knows what data it needs and where it will come from

It wasn’t flashy.
No huge new feature.
But this was the moment PakUni stopped being a “demo app” and started becoming real.

I also learned something important:
Coding is only half the work.
The other half is making sure your app is ready for reality — messy data, edge cases, and scale.

Next up:
➡️ Connecting the actual university dataset
➡️ Making search & filters work on real data
➡️ Slowly unlocking merit + scholarship features

Still building. Still learning. Still shipping. 💪

Devlog 2 – PakUni

While working on PakUni, I face an unexpected problem. : there was no single, reliable, and updated dataset of all Pakistani universities available online. Information was scattered across outdated websites, PDFs, and incomplete lists. It made me realize that without fixing this first, building a reliable app wouldn’t be possible.

So I paused feature development and focused on the foundation.

I spent around 5+ hours collecting and verifying data of all 258+ Pakistani universities, including universities names, official websites links, logo links and further basic details . This part doesn’t show up in WakaTime because it wasn’t coding, but it was necessary work. I organized everything into an Excel sheet, which I’m attaching to show the progress.

Alongside that, I also spent about 3 hours coding. During this time, I cleaned my app structure, improved navigation between screens, fixed UI issues on the home page, and prepared the codebase so it can later connect smoothly with real university data.

This step matters because PakUni depends on accuracy. Without trustworthy data, features like university search, merit calculations, and scholarships wouldn’t mean much.

I realized sometimes progress isn’t just writing code, it’s doing the groundwork that makes real building possible.

Devlog 1 – PakUni
Hey everyone! I recently started working on PakUni, a mobile app to make life easier for Pakistani students.

While applying for universities, I realized how confusing it is for pakistani students to find accurate information about programs, merit calculations, and application steps. I often had to switch between websites, PDFs, and forums, sometimes getting outdated or incomplete info. That’s when the idea for PakUni came into my mind; a single platform with everything a student needs.

What I’ve done so far (13 hours 30 minutes):

Planned core features: university search, merit calculator, Scholarships, student dashboard
Set up GitHub repository and organized project structure
( https://github.com/humna-mustafa/PakUni )
Designed and built the functional home page with buttons for main features and basic navigation
Debugged issues and improved app structure
Learned more about coding practices, UI design, and planning app step by step

Why this matters:
PakUni can save students time and confusion, letting them focus on their goals instead of searching for information.

I’m working on my first project! This is so exciting. I can’t wait to share more updates as I build.