Starz University Mobile App

It started with a rainy ride

Two years ago, riding my motorbike to campus, I got caught in heavy rain. By the time I arrived, my student handbook and payment receipts were completely ruined, and there was no way to replace the handbook until the next semester. Standing there soaked, I asked a simple question: how many other students go through this same hassle, and why hadn't the university offered a smarter solution?

That question became the Starz University Mobile App, an app born from a real student's need and crafted to make essential information and services accessible anytime, anywhere. It isn't just an app to save you from soggy papers; it's a tool designed to make university life easier, smarter, and more connected.

A fragmented campus

The problem was never a lack of effort. Like many Liberian organizations, the campus kept operations moving with paper files, spreadsheets, phone calls, WhatsApp messages, personal memory, and constant follow-up.

The real friction was fragmentation: notices, academic information, library resources, social communication, and records all lived in separate places. Students navigated between physical notice boards, separate portals, and unofficial channels just to find or verify a single answer. Methods like these can survive while an organization is small, but growth exposes their weaknesses, information becomes hard to verify, responsibility becomes unclear, and simple questions pass through several people before an answer can be trusted.

A digital platform should not insult the people who managed the old process. It should preserve what works, remove unnecessary friction, and make accountability easier.

Workflow before features

Before thinking about features, I had to understand the workflow. I kept returning to a set of questions:

• Who creates the information?
• Who checks it?
• Who is allowed to change it?
• What happens when the internet is slow?
• What happens when a user makes a mistake?
• What should management see, and what should stay private?

These aren't decorative planning exercises, they decide whether the final system supports the organization or creates a new kind of confusion. A weak understanding of the workflow cannot be repaired by a beautiful interface. Design can hide confusion for a while, but users eventually feel every unclear rule.

Architecture & engineering

The parts users never praise are the parts that decide whether a system lasts. Information needed a clear structure. User roles needed boundaries. Important actions needed validation. Records needed to stay understandable long after the person who created them had moved on, and the system needed room to grow without turning every future improvement into a complete rebuild.

I designed for real conditions, not ideal ones: different devices, different levels of digital confidence, and unreliable internet. And I treated data with respect, every record has a purpose, an owner, an access rule, and a retention plan, backed by backups, audit trails, and clear permissions. The public judges technology by what appears on the screen, but professional responsibility includes what happens behind it.

A fast demonstration can impress people for one day. A thoughtful foundation protects the project for years.

Measurable impact

What it taught me

I'm proud of the technical growth, but I value the professional lessons even more. Software development is rarely only about writing code, the real work begins with understanding people, pressure, habits, and the consequences of getting a decision wrong.

Clients and developers often use the same words while imagining different things, so my job is to ask respectful questions and help stakeholders separate symptoms from root causes. I stopped treating revision as proof that the work failed; more often it means the project has moved from assumption to understanding. And completion isn't launch day, adoption, training, maintenance, and support are what turn a product into infrastructure.

The strongest portfolio is not a long list of technologies. It is a record of problems understood and responsibilities handled well.