Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
Modernization and Removing Inconsistencies
During the development process, notable inconsistencies emerged in the user interface (UI) elements across the iOS, Android, and Web platforms. These discrepancies were not only present between the different platforms but also across various screens within the app itself. To address this issue and ensure a cohesive and consistent design experience throughout the application, I took the initiative to create a comprehensive component library using Figma.
The component library I was creating in Figma served as a single source of truth for the app's design system. It provided a clear reference for how each UI element should look and behave, ensuring that designers and developers across different teams and platforms could easily adhere to the established design guidelines.
Within the component library, I meticulously documented and organized the various UI components, specifying their visual properties, interactions, and usage guidelines. This approach not only facilitated a cohesive design language but also streamlined the development process by reducing the need for redundant work and minimizing the risk of introducing new inconsistencies.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
One of the most important aspects of design is managing interruptions. These interruptions can be urgent, help progress a current task, or provide information the user cares about. Although the app's code was optimized for reuse, it led to a situation where all notifications, wewere delivered as a series of interruptions. This either completely blocked the user from accomplishing their task or, at the very least, disrupted their thought process.
In order to address this challenge, we polished our approach related to delivering notifications. Alerts got structured based on their severity and pertinence to the user's current activity. Immediate alerts like ID confirmation or unfinished setup surfaced as overlays. These provided a chance to delay the task, however, it would reappear in the next session, and remained vital for initiating transactions. Conversely, non-emergency notifications were shown in a less intrusive style: a task list on the main page. This strategy allowed the user to survey all transactions demanding their attention, without deviating their focus from the current task. We succeeded in consolidating seven pop-ups into a single list which uniquely improved the cumulative user experience of the app.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
The app's user journey was far from perfect, to put it mildly. Unnecessary and obsolete selections were present in the navigation. For example, the Invoices selections and the New Invoices feature both led the user to practically identical pages, with the slight variation of displaying a dropdown list when the add button was tapped.
Furthermore, a significant issue repeatedly encountered by our customers was finding information related to payments, timelines, and reaching the agreement after concluding the deal. Many issues were addressed with the implementation of several changes to the navigation panel.
Payment Issues and Navigation Bar Update
In the first update of the navigation bar, the billing section was moved from the reporting tab to its own section. This change aimed to address payment issues.
Document Upload Process
QuickFi required users to provide additional fiscal details during financing. Users could upload a PDF or a snapshot of the requested documents. However, users were only prompted to upload documents at login, with no alternate access method within the app. This limited prompt visibility was a significant drawback.
Version 2 Navigation Bar Changes
In Version 2, the Billing and Documents sections were merged into a "More" section. This was not optimal, as users struggled to locate the billing section.
New Invoice Button and Navigation Bar Revamp
The "New Invoice" button lost its value after QuickFi onboarded partners and dealerships. Most users accessed the app to complete pre-setup deals with invoices already uploaded. I suggested a revamped layout to streamline the navigation bar aesthetics and functionality.
By moving the "New Invoice" button to a Floating Action Button (FAB) on the Invoices page, users retained the ability to upload invoices for standalone transactions. This change freed up space on the navigation bar to accommodate both billing and document sections individually.
Final Adjustments and Integration
Ultimately, the document segment was incorporated into Billing through a thorough overhaul. This modification integrated a third-party system for efficient creation of invoices, improving the Billing page's overall functionality. To signify a document request, a badge was added to the Billing tab.
