v3.0.6 · Features
2 min read
Gradle auto-reads version from `package.json` — single source of truth, no manual sync needed
Problem
Gradle auto-reads version from `package.json` — single source of truth, no manual sync needed
Pain point
Features
Solution
Android Release Pipeline
• Gradle auto-reads version from `package.json` — single source of truth, no manual sync needed
• Added `build:android` script for one-command signed APK builds
Example
• New GitHub Actions workflow: push a `v*` tag to automatically build and publish signed APK to GitHub Releases
• Enabled R8 code shrinking and resource optimization for smaller APK size
• Added Capacitor-specific ProGuard keep rules
App Icon
• Replaced default Android robot icons with Locusify brand logo across all density buckets
• Proper adaptive icon foreground with safe-zone padding
Bug Fixes
• Upgraded AGP to 8.9.1 and compileSdk to 36 for `androidx.browser` compatibility
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: Android Release Pipeline • Gradle auto-reads version from `package.json` — single source of truth, no manual sync needed • Added `build:android` script for one-command signed APK builds. 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