What Are Patterns in JDP?

Source: Dev.to

Introduction

Insurance applications often contain repetitive, predictable flows. Re‑creating the same steps for every new project wastes time and introduces unnecessary complexity.

What Are Patterns in JDP?

• Analogy: If Jutro components are LEGO bricks, patterns are pre‑built LEGO sets (e.g., a car, a house, a spaceship) that you can customize with colors and stickers.
• Definition: Patterns are reusable, ready‑to‑go UI flows built from multiple Jutro components, specifically designed for common insurance journeys.
• Purpose: They eliminate the need to reinvent multi‑step forms, document‑upload flows, payment steps, quote summaries, review pages, and more.

Common Insurance Flows Covered by Patterns

• Customer information
• Addresses & contacts
• Vehicle / property details
• Coverages
• Payment
• Review & confirm
• FNOL (First Notice of Loss)
• Claims submission
• Multi‑step workflows

Benefits of Using Patterns

• Time savings – developers skip building the same UI repeatedly.
• Reduced complexity – fewer moving parts to maintain.
• Fewer bugs – proven, tested flows.
• Less friction – fewer arguments and weekend deployments.
• Developer sanity – focus on business logic instead of layout and navigation.

Typical Patterns You’ll Use

• FNOL submissions
• Quote & buy processes
• Payment processes
• Add / edit / delete flows
• Multi‑step wizards
• Timeline flows
• Coverage selection
• Document upload + validations
• Policyholder details updates
• Review & summary screens

These patterns are common because every carrier needs them, and the core logic rarely changes.

When to Use a Pattern

Use a pattern when the flow is:

• Multi‑step
• Repetitive
• Data‑heavy
• Tied to a backend entity (policy, claim, account)
• Predictable and already known to users

When Not to Use a Pattern

Avoid patterns if:

• You need a highly custom UI.
• You’re designing a unique section that doesn’t fit the mold.
• Animations or specialty layouts are more important than the underlying structure.

Summary

For the majority (≈ 80 %) of insurance flows, patterns in JDP provide reusable UI sequences that let developers skip repetitive work and concentrate on the actual insurance logic rather than layout, spacing, or step navigation.