Haluka

Context

Haluka was built around a specific operational problem: Islamic boarding schools needed a better way for students and families to stay connected through a supervised phone-stall model.

The product included a mobile app used by students and two web applications for cashier and admin workflows.

Challenge

This was not just a communication app. It had to respect institutional rules, family expectations, and operational controls.

Students needed a simple way to connect. Cashiers needed workflows that could support daily use. Admins needed enough control to keep the system reliable and accountable.

Approach

I handled the end-to-end web and mobile app design process and supported usability and user acceptance testing.

The design needed to make the core action easy while still accounting for different user roles. That meant separating student, cashier, and admin needs early, then shaping flows that felt direct within each context.

Outcome

The project turned an offline phone-stall interaction into a digital product system with mobile and web surfaces.

The strongest design lesson was role clarity. When a product serves multiple users in the same service chain, the interface has to make each person’s responsibility obvious.

What I Would Refine Next

This case study should eventually include task flows, role-based screenshots, testing notes, and examples of changes made after usability or acceptance feedback.