Other App Components

These are the remaining components provided by the Feather app on top of qnr-framework. They handle specific business logic that is not covered by the core input/selection/flow components or the major app components (Quote Page V2, Checkout, Processing).

---

Email (EMAIL)

Full email collection step with account detection. When the user enters their email:

• If the email matches an existing Feather account, a login modal is shown so the user can sign in and link the new policy to their account
• If the email is new, the component proceeds and creates an account during checkout

This is the standard email step for signup questionnaires.

Layout: Centered

---

EmailBasic (EMAIL_BASIC)

Simple email input without the login detection flow. Just collects an email address as a plain text field. Used in flows where account linking is not needed (e.g., lead generation, claims).

Layout: Centered

---

Review (REVIEW)

Summary page showing all collected answers before final submission. Auto-generates review sections by reading the questionnaire answers and applying a transform mapping to create human-readable labels.

Each section groups related answers (personal details, coverage preferences, etc.) and lets the user navigate back to edit specific answers.

Layout: Standalone

---

HasPolicy (HAS_POLICY)

Checks whether the current user already has an active policy of the same insurance type. Used to prevent duplicate purchases.

If the user already has the policy, they see a message explaining the situation with options to manage their existing policy or continue anyway.

Layout: Centered

---

CoveredGroup (COVERED_GROUP)

Visual card-based selection for choosing who is covered by the policy. Renders large, illustrated cards for options like:

• Just me
• Me + partner
• Family (me + partner + children)
• Single parent + children

Each card typically includes an illustration and description of who is included.

Layout: Centered

---

EffectiveDateDropdown (EFFECTIVE_DATE_DROPDOWN)

Dropdown for selecting a coverage start date. The available dates are calculated based on business rules specific to the insurance vertical (e.g., “first of next month”, “any date within the next 3 months”, “retroactive up to 2 months”).

Layout: Centered

---

IbanForm (IBAN)

IBAN (International Bank Account Number) input with real-time validation. Validates the IBAN format and displays the associated bank name when valid.

Layout: Centered

---

Tally (TALLY)

Embeds an external Tally.so form inside the questionnaire. Used for complex surveys, feedback collection, or forms that are easier to build in Tally’s form builder.

The embedded form communicates back to the questionnaire when completed, allowing the flow to continue to the next question.

Layout: Standalone

---

UploadDocuments (UPLOAD)

Single file upload with preview. The user selects or drags a file, sees a preview (for images) or filename, and can remove and re-upload before continuing.

Layout: Centered

---

MultiUpload (MULTI_UPLOAD)

Multiple file upload with a legal consent checkbox. The user can upload several files at once, and must check a consent box (e.g., confirming the documents are authentic) before proceeding.

Layout: Centered

---

CarLookup (CAR_LOOKUP)

Vehicle lookup by license plate for Germany. The user enters their license plate number, and the component fetches vehicle details (make, model, year, engine) from an external API. The retrieved data is stored as the answer and used in subsequent pricing and checkout steps.

Layout: Centered

---

CarLookupSpain (CAR_LOOKUP_SPAIN)

Vehicle lookup by license plate for Spain. Same concept as CarLookup but using Spanish plate format and a different vehicle data provider.

Layout: Centered

---

CancellationReview (CANCELLATION_REVIEW)

Review step specifically for policy cancellation flows. Similar to the general Review component but includes a submitKeys mapping that defines how questionnaire answers are transformed into the cancellation API request payload.

Layout: Standalone

---

AddToCart (ADD_TO_CART)

Adds the current product configuration to the user’s cart for multi-product flows. Used when a single session can result in purchasing multiple insurance products.

Layout: Standalone

---

Other extended components

These components are used internally by the app and may not have dedicated Strapi question types:

• CustomIntro — Enhanced version of the INTRO component with richer layout options, custom illustrations, and more flexible content sections. Automatically used instead of IntroForm in certain questionnaires.
• CustomBox — Custom content box component for displaying formatted information within a question page.
• ValidatedInputForm — Input component with enhanced inline validation feedback.
• Download — Document download step that presents a file for the user to download before continuing.

See also

• App Extended Components Reference – technical reference with component registration details
• Question Types Reference – Strapi-side specs for all question types including these
• Architecture Overview – how app-extended components fit into the rendering pipeline