v1.4.0 · Features
2 min read
Replaced canvas-based recording with the browser Screen Capture API (`getDisplayMedia`)
Problem
Replaced canvas-based recording with the browser Screen Capture API (`getDisplayMedia`)
Pain point
Features
Solution
Screen Capture Recording
• Replaced canvas-based recording with the browser Screen Capture API (`getDisplayMedia`)
• Recording now captures the actual browser tab, ensuring perfect visual consistency between playback and recorded video
Example
• Eliminated ~900 lines of manual canvas drawing code (intro, photo card, avatar, watermark, transport badge)
• Audio is suppressed and cursor is hidden during recording for a clean output
• Tab switching is prevented during capture via `surfaceSwitching: 'exclude'`
Recording UI Improvements
• Menu button and replay controls are hidden during active recording for a distraction-free video
• DOM watermark ("Powered by Locusify") is displayed during recording and naturally captured
• Recording automatically stops 2 seconds after replay completes
Refactor
• Removed `mediabunny` dependency (MP4 via WebCodecs) — no longer needed
• Removed `iconPaths.ts` canvas SVG rendering data — no longer referenced
• Added `recordingActive` state to replay store for centralized recording UI control
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: Screen Capture Recording • Replaced canvas-based recording with the browser Screen Capture API (`getDisplayMedia`) • Recording now captures the actual browser tab, ensuring perfect visual consistency between playback and recorded video. 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
If the update solves your workflow pain point, test it with your next trip album.
Try Locusify with your travel photosFrequently 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 morev3.1.1 · Features
Real-time nearby explorer markers on the map with clustering support
Read morev3.1.0 · Features
Redesigned replay photo panel with polaroid-style ticket cards, tape decorations, and photo filters
Read more