Streamlining the Onboarding Flow in Breniapp

Introduction

The onboarding process is often the first experience a user has with a product. In Breniapp, a significant effort was undertaken to align the onboarding flow with updated specifications, resulting in a more focused and efficient user experience.

Removing Redundant Fields

The initial phase of the restructure involved removing several fields from the early sections of the onboarding process. This cleanup focused on eliminating information that was either redundant or not critical to the initial setup. Specifically, the following fields were removed from Section 1:

• industry
• country
• content_language
• value_proposition
• differentiator
• product_categories
• price_range
• service_lines
• ideal_client_type
• average_ticket
• site_language

Similarly, Section 2 saw the removal of:

• customer_desires
• product_knowledge_level
• custom_objections

Section 3 had the tone_intensity slider removed, further simplifying the process.

Restructuring Sections and Adding New Elements

The reorganization extended beyond mere removal. Section 4, now focused on Visual Identity, introduced logo_upload while removing image_preferences, visual_formality, and typography. Section 5 was streamlined to focus solely on Visual DNA, incorporating visual_references_upload and visual_dna. Subsequent sections were renumbered and their content redefined:

• Section 6 became Content Strategy, encompassing content_pillars, theme_proportions, preferred_formats, posting_frequency, and copy_style.
• Section 7 is now dedicated to Campaigns.
• Section 9 now handles References, including content_referents, brandbook, inspiration_links, and competitor_links, while removing dislike_links and graphic_pieces_upload.
• Section 10 now addresses Platforms & Goals, featuring primary_platform, primary_cta, and secondary_cta, while removing main_goals.

Visual styles were updated to align with six specification options, and preferred formats were refined to four options. A new "otro" (other) option was added to posting frequency. The sidebar labels were also updated to reflect the new section order.

Code Example: Defining Allowed Posting Frequencies

To illustrate how these changes might be reflected in the codebase, consider the following example of how the allowed posting frequencies could be defined in PHP:

<?php

namespace App\Enums;

enum PostingFrequency: string
{
    case Daily = 'daily';
    case Weekly = 'weekly';
    case Monthly = 'monthly';
    case Other = 'otro';
}

Translation and Testing

To ensure a consistent user experience across different languages, translations for the visual_dna section were added in Spanish, English, German, and French. Tests were updated to reflect the new flow and ensure the application's stability.

Results

By removing unnecessary fields, reorganizing sections, and adding new elements, the onboarding flow in Breniapp is now more aligned with the Lovable specification, providing a smoother and more efficient experience for new users.

Next Steps

Consider gathering user feedback on the updated onboarding flow to identify areas for further improvement. A/B testing different variations of the flow could also provide valuable insights into what works best for your target audience.