Omniwallet is a mobile financial-management concept that evolved across three courses at Santa Clara University. 

The project began in EMGT 285 — Managing Business Relationships, where I developed the initial business concept with 2 other students. I then expanded the idea in ARTS 75 — Basic Graphic Design, exploring the brand identity, visual direction, and a broader set of product experiences. Finally, I brought the concept into CSEN 268 — Mobile App Development, where the scope was narrowed to create a mobile application that could realistically be implemented.

Because each stage had a different purpose, the final CSEN 268 application does not include every feature explored during the earlier design stage. Instead, it represents how the original concept was refined as it moved closer to implementation.

Omniwallet began in EMGT 285 — Managing Business Relationships as a concept for bringing multiple financial activities into one place.

The idea was to create a centralized experience where users could manage different aspects of their finances within a single application.

At this stage, the focus was on developing the overall business and product concept before moving into the visual and technical development of the application.

Course: EMGT 285 — Managing Business Relationships

As I continued developing Omniwallet, I mapped out the application's overall structure and how users could move between its different areas. 

The flow begins with the Welcome screen and branches into Log In or Sign Up, leading into the Home experience. From there, users can access Accounts, Transactions, Bills, Investments, Tracking, and Settings.

I also mapped secondary actions within these areas, including viewing and managing accounts, paying and adding bills, reviewing investments, setting a budget, and managing personal, security, and notification settings.

In ARTS 75 — Basic Graphic Design, I began translating the Omniwallet concept into a visual identity and mobile interface.

I explored different directions for the app icon before refining the concept into an image representing a credit card and driver's license. The visual system centered around blue and white, creating a clean and recognizable identity for the financial application.

The initial interface used blue backgrounds with white typography and graphics. After feedback, I shifted toward a predominantly white interface with blue typography and interface elements.

This change introduced more white space while maintaining the visual language established for Omniwallet.

During ARTS 75, I explored a broader version of what Omniwallet could become.

The Home experience organized the product around four major financial areas:

Accounts · Transactions · Bills · Investments

Additional navigation provided access to Tracking and Settings.

Home

The Home Screen was designed as a central dashbaord, giving users an overview of their finances while providing direct access to the application's major functions.

Accounts

The Accounts experience allowed users to view their cards and account information while also exploring additional tools such as a credit-card quiz and a pathway for finding another card.

Transactions

The Transactions experience focused on making financial activity easier to browse. Users could search, sort transactions by date, and filter between all, sent, and received transactions.

Bills

The Bills experience organized recurring expenses into categories such as Gym, Phone, Housing, Internet, Electricity, and Water. It also included options to add bills, pay bills, and surface payment notifications.

When Omniwallet moved into CSEN 268 — Mobile App Development, the focus shifted from exploring everything the product could potentially do to deciding what we could realistically implement.

The broader ARTS 75 concept included multiple areas and supporting features. For CSEN 268, we narrowed the experience to a more manageable scope that could be developed within the course project.

This meant that the later prototype looks different from the earlier ARTS 75 work.

Rather than being a completely different design, the CSEN 268 version represents the next stage of Omniwallet's development: taking a broad product concept and refining it into a more focused, implementable application.

The evolution

EMGT 285

Business & product concept

↓

ARTS 75

Visual identity & broader product exploration

↓

CSEN 268

Scoped mobile prototype & implementation

In CSEN 268, Omniwallet moved from primarily visual exploration toward an actual mobile application.

The Figma prototype represents this later stage of the project, with the experience adapted to the scope we could realistically implement.

Rather than trying to build every feature from the earlier concept, we focused on creating a functional mobile experience within the project's constraints.

The CSEN 268 project took Omniwallet beyond a visual prototype and into implementation.

The Figma prototype shows the designed experience, while the working application demonstrates how the concept was translated into an actual mobile product.

View Figma Prototype

Watch Demo

View GitHub Repository

Omniwallet evolved significantly as it moved through three different courses.

What began as a broad business concept became a visual and product-design exploration before being narrowed into a mobile application that could be implemented.

The project taught me how to take a large product idea, structure its experience, establish a visual direction, and make decisions about scope and feasibility when moving from design toward implementation.

View our demo on YouTube ->