A digital fleet operations solution designed for a large-scale industrial environment to improve coordination between an operations control team and vehicle drivers working across the site.

The solution consists of two connected applications:

Together, both applications create a connected workflow between the control team and drivers.

Coordinating multiple vehicles within a large industrial environment requires continuous communication between drivers and the operations team.

The control team needs visibility into vehicle availability, assignments and ongoing activities. Drivers, meanwhile, need clear instructions without being overwhelmed by unnecessary operational information.

This created two very different UX requirements:

The challenge was to design both experiences as part of the same system while ensuring each interface was appropriate for its user's working environment.

I worked across UI/UX design and front-end implementation, translating operational requirements into interfaces suitable for real-world industrial use.

My responsibilities included:

• Understanding existing fleet and driver workflows.
• Translating operational requirements into user flows and interfaces.
• Designing the fleet operations dashboard.
• Designing the tablet experience for drivers.
• Developing responsive front-end interfaces.
• Creating reusable UI components and interaction patterns.
• Integrating interfaces with backend services.
• Collaborating with stakeholders during requirement discussions and UAT.
• Refining interfaces based on operational feedback.
• Supporting production implementation.

The Fleet Operations Dashboard acts as the central interface for teams responsible for coordinating vehicle activities.

It provides operators with a shared view of vehicle availability, current assignments and operational statuses.

Rather than simply presenting large amounts of data, the interface was designed to help operators quickly answer:

Clear information hierarchy, status indicators and consistent interaction patterns help users scan operational information and identify important changes quickly.

This was particularly important because operators may need to monitor several activities simultaneously.

The Driver App extends the system from the operations centre into the field.

Dedicated tablets installed in vehicles provide drivers with information about their current tasks and allow them to update the progress of their assignments.

Unlike the operations dashboard, the driver interface intentionally exposes only the information needed for the immediate task.

One of the most interesting UX challenges was designing two applications for users participating in the same workflow but requiring completely different levels of information.

The operations team needs visibility and control.

The driver needs clarity and direction.

Instead of creating a single interface for everyone, each application was designed around its user's responsibilities.

The dashboard prioritises information density, monitoring and coordination.

The driver application prioritises readability, immediate actions and simplicity.

Both experiences remain connected through the same underlying operational workflow.

Vehicle-based applications also introduce challenges that are uncommon in traditional office software.

Connectivity can become inconsistent as vehicles move throughout a large industrial environment.

During testing and production observation, application and location data were analysed to understand delayed updates, temporary connection interruptions and synchronisation behaviour.

These findings helped inform how the application handles connectivity and communicates system states to users.

One of the key lessons from the project was:

The user experience also needs to remain understandable when information is delayed or temporarily unavailable.

The solution created a connected digital workflow between a central operations team and drivers working in the field.

The Fleet Operations Dashboard provides the visibility required to coordinate activities, while the Driver App translates those activities into a focused experience for drivers.

The project demonstrated how UI/UX can simplify complex operational processes without removing the information users need to make decisions.

This project strengthened my experience designing role-based enterprise applications and operational interfaces.

More importantly, it taught me to consider the environment surrounding an interface.

Network conditions, hardware, physical environments and the context in which users interact with software can be just as important as the visual design itself.

It reinforced the approach I bring to UI/UX development today:

Memoira is a digital invitation platform designed to provide couples and event organisers with personalised web-based invitations.

Instead of sending guests a static image or generic invitation link, each event receives its own personalised web experience.

An invitation can be accessed through a dedicated event subdomain such as amin-juliana.memoira.my.

The goal was to make digital invitations feel more personal and memorable while keeping them simple for guests to access from their phones.

Most digital invitation experiences need to balance two very different requirements.

For the event owner, the platform needs to provide customisation and event management capabilities.

For the guest, the experience should require almost no learning curve. Guests should be able to open a link and immediately understand the event details and available actions.

This meant the product needed to hide the technical complexity behind a simple mobile-first experience.

Memoira is an end-to-end product project where I worked across both product design and technical implementation.

My work included:

• Defining the overall product concept.
• Designing the invitation experience.
• Designing mobile-first interfaces.
• Developing reusable React components.
• Creating animations and interactive experiences.
• Planning the event and invitation data structure.
• Implementing dynamic invitation pages.
• Exploring payment integration.
• Configuring production deployment and custom domains.
• Designing the architecture for dynamic event subdomains.

Each invitation acts as a personalised event website rather than a static invitation.

The experience can combine event information, visual storytelling and interactive functionality within one mobile-friendly page.

The interface is intentionally designed around guests first. Important information should be immediately accessible without requiring users to create accounts or understand how the underlying platform works.

One of the more interesting engineering challenges was supporting dynamic event subdomains.

Instead of using URLs such as memoira.my/event/amin-juliana, the platform was designed around amin-juliana.memoira.my.

This required thinking beyond the UI itself and considering DNS configuration, wildcard subdomains, deployment architecture and how event information should be resolved dynamically.

Memoira allowed me to approach development from a product perspective rather than only implementing predefined requirements.

I had to think about the complete experience: branding, interface design, technical architecture, deployment, domains and how the product could eventually operate as a scalable platform.

It represents the intersection between my background in visual design and my work as a software developer.