Back to blog
Updates / Changelog
Comparisons & Updates

v3.0.3 · Features

2 min read

Added forgot password flow: enter email to receive a reset link via Supabase

Problem

Added forgot password flow: enter email to receive a reset link via Supabase

Pain point

Features

Solution

Forgot / Reset Password

• Added forgot password flow: enter email to receive a reset link via Supabase

• Added standalone reset password page that parses Supabase hash fragment tokens

Example

• Added password reset button for logged-in users in account drawer with 60s cooldown

• Password complexity validation: 8+ characters with uppercase, lowercase, and numbers

Password Login

• Added password-based login and signup alongside existing OTP flow

• Login method tabs (Verification Code / Password) in the login drawer

• Forgot password view integrated within the password login form

Privacy Consent

• Added privacy policy and terms of service checkbox to login drawer

• All submit actions guard against unconsented state with toast notification

Bug Fixes

• Fixed invisible error text by replacing undefined `text-destructive` with `text-red`

• Fixed signup password mismatch showing field label instead of error message

• Fixed confirm password input not clearing error state on change

• Fixed auth callback white screen with parallel requests and loading state

Refactor

• Extracted shared `useCooldown` hook for 60-second rate limiting across 3 components

• Added `Checkbox` UI component (Radix-based)

Decision Criteria at Bottom Funnel

Bottom-funnel readers are evaluating confidence, switching cost, and output predictability. Generic feature lists are rarely enough.

Content should prioritize decision dimensions: onboarding time, migration friction, and quality consistency.

For "locusify update", define clear evaluation criteria so readers can choose quickly based on their workflow reality.

Comparison Method That Builds Trust

Use one real dataset across tools and compare three metrics: completion time, correction workload, and final publish quality.

A practical baseline flow remains: Forgot / Reset Password • Added forgot password flow: enter email to receive a reset link via Supabase • Added standalone reset password page that parses Supabase hash fragment tokens. Keep claims tied to observable process outcomes.

Write conclusions as fit-by-scenario, not absolute winner claims. This increases credibility and conversion quality.

Bottom-Funnel Conversion Actions

End with explicit actions: test run, import real assets, export first version. Concrete actions move decisions forward.

Include risk notes and fallback paths. Balanced framing often converts better than aggressive claims.

Interlink to tutorial and case-study pages to complete the comparison -> trial -> validation loop.

Target keywords

locusify updatelocusify changeloglocusify v3.0.3

If the update solves your workflow pain point, test it with your next trip album.

Try Locusify with your travel photos

Frequently asked questions

What is the fastest way to start with locusify update?

Use one recent trip folder and run the full flow once: import, timeline check, outlier cleanup, and short replay export.

What if some photos do not contain GPS metadata?

Build the core route from geotagged photos first, then place non-geotagged images as chapter visuals instead of route points.

How do I make outputs more shareable on social channels?

Keep runtime concise, start with route overview, highlight key stops, and export directly in the target aspect ratio.

Where does Locusify fit in this workflow?

If the update solves your workflow pain point, test it with your next trip album.

Related articles

v3.2.0 · Features

Add Pricing Drawer for plan management and redemption flow

Read more

v3.1.1 · Features

Real-time nearby explorer markers on the map with clustering support

Read more

v3.1.0 · Features

Redesigned replay photo panel with polaroid-style ticket cards, tape decorations, and photo filters

Read more