Hwkui Laravel Package

Product Decisions This Supports

• Onboarding and activation: The Tour widget is the core value here — guided, step-based walkthroughs for new users or newly shipped features. That directly supports activation-rate and time-to-value OKRs.
• Copy and CTA experimentation: The new options for widget text and next-button colors let PMs/marketing adjust tour messaging and visual emphasis without an engineering cycle. Useful for lightweight A/B tests on onboarding copy, or for localizing/branding tours per surface.
• SPA-navigation reliability: The wire:navigate fix is the more strategically relevant change. If your app uses Livewire's SPA-style navigation, tours that broke or lost state between page transitions were a real defect class. This removes a common source of "the onboarding flow is broken again" support tickets.
• Build vs. buy for in-app guidance: This is a Livewire-native alternative to bolting on a JS tour library (Shepherd, Intro.js, Driver.js) and writing lifecycle glue. The decision hinges on whether a thin, in-stack component beats a richer external tool.
• Roadmap framing: Treat 1.1.3 as a signal that the Tour widget is actively maintained and being hardened for real-world usage — not as evidence of a broad, mature design system. Scope any roadmap commitment to "onboarding/tours," not "adopt as our UI kit."
• Not supported by this release: anything about accessibility conformance, analytics instrumentation, tour targeting/segmentation, or long-term maintenance guarantees. Those need separate evaluation before they inform a roadmap decision.

When to Consider This Package

Consider it when:

• You are on Laravel + Livewire (ideally Livewire 3 with wire:navigate) and want tours/onboarding without introducing a separate JS framework or a third-party SaaS dependency.
• Your tour needs are simple-to-moderate: linear steps, custom copy, branded next-button styling.
• You want product/marketing to own tour text and CTA emphasis through configuration rather than code changes.
• You are willing to pilot on one flow and measure completion/activation before broader rollout.

Look elsewhere when:

• You need branching/conditional tours, user-segment targeting, or built-in experimentation and funnel analytics — this release shows no evidence of those.
• You require documented accessibility conformance (focus management, ARIA, keyboard traps) for onboarding; verify explicitly, do not assume.
• Tours must persist across full page reloads or a non-Livewire, multi-page app — wire:navigate support implies SPA-style navigation is the supported path.
• You are not on Livewire, or you already have tour primitives in an established design system.
• Package health is unverifiable: check release cadence, issue responsiveness, test coverage, and whether this is a single-maintainer project, before making it a dependency in a critical onboarding path.

Upgrade risk: 1.1.3 is a patch release with a bug fix and additive options. No breaking changes are indicated; upgrading from 1.1.2 looks low-risk. Regression-test any tour that spans SPA navigation.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, in-stack way to improve onboarding. It lets us ship guided tours and iterate on their wording and call-to-action styling without engineering work, and the latest patch fixes a defect where tours broke during in-app navigation — a frequent source of a broken first-run experience. Recommendation: fund a scoped pilot on one onboarding flow with completion and activation as success metrics, not an org-wide adoption.

For engineering: A Livewire-native component rather than an added JS dependency, which keeps the frontend stack small. The wire:navigate fix addresses tour state across SPA transitions, and the new options are additive configuration for text and next-button color — no breaking changes in 1.1.3. Before committing, we want a read on test coverage, maintenance cadence, and accessibility behavior; the pitch is a contained pilot behind one flow, not a platform bet.

For product/marketing: You get direct control over tour copy and CTA emphasis, which shortens the loop between "the onboarding message isn't landing" and a shipped change. Constraint to plan around: no built-in targeting, segmentation, or analytics from what we can see — measure with our existing instrumentation.