Rebranding Walkthrough

Introduction

  • Purpose of Discussion: Showcase the capabilities of existing APIs and applications built using CDL APIs.

  • Proof of Concept: The application is a demonstrator to illustrate potential functionalities.

Transition to New User Interface

  • User Experience Changes: Transitioning from Windows to a Mac can be challenging, especially when familiar tabs and window configurations change.

  • Adaptation Process: Users are encouraged to utilize gestures to improve efficiency, with the aim to become proficient in the new interface.

Application Overview

  • Functionality of Built Application: Built to showcase what can be achieved with existing CDL APIs.

  • Interaction with Astra: The front end interfaces with the Astra environment through APIs.

User Interface Demonstration

  • Multi Quote and Buy Application:

    • Once initiated, the application allows users to obtain quotes for various insurance types.

    • Mock Data: The application returns stub JSON data, simulating a vehicle lookup without actual data retrieval.

    • Quote Request Process:

    1. Upon pressing "get quote," a request is sent to Strata for a specified vehicle.

    2. The application then waits for a response that includes price and associated data.

    3. A customer ID is generated in the response which is used for subsequent queries.

Multi-Policy Quoting

  • Customer ID Utilization::

    • Once a customer ID is retrieved, it is used to fetch quotes for additional insurance types (vehicle, bike, home, van).

    • Example: After getting a quote for one vehicle, the user can quickly generate quotes for other policies without resubmitting full information (e.g., address).

Custom Branding for Client Demonstrations

  • Client-Specific Customization: Each demo is tailored directly to the client's brand:

    • Customization involves altering the UI to match the client’s branding during demonstrations.

    • The development team has flexibility in branding adjustments based on client requests.

Theming and UI Changes

  • Theme Switching: Users can change themes and branding easily—.

    • Mock Presentations: Used for showing clients the product in their own branding.

    • Visual Elements: The UI can be modified to reflect the appropriate colors, fonts, logos, etc. to suit specific clients.

Administration and Theme Management

  • Admin Capabilities:

    • Admins can alter and customize themes depending on client specifications.

    • Feedback Mechanism: Features like a call to action button can be added to policies to enhance interactivity.

Chrome DevTools Integration

  • Usage of Development Tools: Allows automation for web interaction and testing through:

    • Automated session management via Chrome DevTools.

    • Generating requirements documentation for branding changes from existing builds.

Building the Insurance Passport

  • Overview: The Insurance Passport app functions as a central hub for customer insurance information:

    • Capable of handling various types of insurance data (vehicles, homes, businesses, etc.).

    • Facilitates user-friendly interactions by reducing the need for redundant data entry.

Efficiency in Data Handling

  • Requirement Minimization: When obtaining quotes (e.g., travel insurance), the system utilizes existing data for efficiency:

    • Data Utilization: User need only provide the travel destination and dates, leveraging already entered information for existing policies to minimize input.

AI Incorporation in Development

  • Parallel Development Tasks: Cairo allows multiple tasks (e.g., code testing, rebranding) to happen simultaneously, enhancing productivity:

    • Users can track ongoing operations and manage workloads efficiently.

Video Documentation and Presentation

  • Video Creation for Client Demos: Demo videos are prepared for client presentations, showcasing the rebranded application effectively.

    • Emphasis on narrating the user journey through the interface to ensure clarity of the product's function.

Collaboration and Team Workflow

  • Best Practices::

    • Encouraged to work collaboratively to enhance learning and efficiency.

    • Sharing knowledge within the team during rebranding tasks and presentations is emphasized to ensure everyone benefits from the experience.

GitLab and Version Control Communication

  • Branch Management: Clear instructions on managing version control processes via GitLab are outlined for team members:

    • Ensures branches are current with main project developments and helps prevent conflicts.

Conclusion

  • Team members will continue improving integration with client requirements as developments progress.

  • Establishing a supportive environment where questions are welcomed to streamline processes and enhance team collaboration.