Skip to main content
li-nk.meli-nk.me
Log inStart free

Roadmap

Coming soon​

Enhanced analytics & tracking​

  • Advanced dashboard with richer metrics and attribution views
  • Time-series reporting with custom ranges
  • CSV/JSON export for external analysis
  • Third-party integrations and data sync

Integrations​

  • Third-party connectors (analytics + marketing automation)
  • API extensions for bulk link management and advanced filtering

Assets library​

  • Save reusable social metadata in separate libraries for:
    • Titles
    • Descriptions
    • Images
  • Mix and match saved title, description, and image while creating links
  • Available image storage depends on the selected plan

Debugging & diagnostics​

  • Easier link debugging workflows for support teams
  • Clearer visual pathways from click → open → destination
  • More actionable diagnostics when a link doesn’t resolve

SDK & universal links​

  • Universal link support that works even without deferred link parameters
  • More consistent behavior across iOS, Android, Flutter, and React Native

Guides & content​

  • More how-to guides, templates, and checklists
  • Case studies that explain usage, outcomes, and ROI

Extra polish​

  • Link scheduling (start/expire windows)
  • Additional governance controls for teams

Why this roadmap exists​

This roadmap helps product, growth, and engineering teams align on what is actively being built so launch plans are realistic. We prioritize features that reduce production risk for deep-link routing, improve attribution confidence, and make operations easier for teams that ship frequently.

If a roadmap item appears here, it means we have already validated demand with customer conversations, support signals, or internal platform constraints. Priorities can still move when reliability or security work needs to take precedence, but this page reflects the current direction for near-term delivery.

Delivery approach​

We ship roadmap items incrementally rather than waiting for one large release. Most features are delivered behind gradual rollouts so teams can validate behavior in production with low risk.

Our standard process:

  1. Problem framing and implementation scope
  2. Internal release with diagnostics and rollback controls
  3. Limited customer rollout
  4. Wider launch after stability checks
  5. Documentation updates in the help center and changelog

This approach keeps quality high while still allowing rapid iteration on analytics, setup flows, and link behavior.

What to expect from updates​

Roadmap entries describe direction, not fixed contractual dates. Exact timing depends on integration complexity, platform review cycles, and any blockers discovered during staging or rollout.

The most reliable source of shipped work is the changelog. Use this roadmap to understand what is being explored and prioritized, then use release notes to confirm what is fully available in production.

Requesting roadmap input​

If your team has a requirement that is not covered here, send it through support with context about:

  • platform(s) affected
  • expected traffic or campaign volume
  • current blocker or workaround
  • timeline pressure and business impact

Clear implementation context helps us prioritize requests that improve reliability and operational value across many teams.

Implementation examples​

  • Attribution upgrade rollout: scope target events, ship to staging first, compare dashboards against baseline, then release to production in phases.
  • Custom domain reliability sprint: start with the highest-volume branded domain, validate SSL and routing, then expand to lower-volume domains after validation checks pass.
  • Developer setup simplification: document environment and auth setup sequence in one checklist before introducing new SDK/runtime guides.

Troubleshooting roadmap execution​

  • If a roadmap item stalls, separate product-scope issues from operational blockers (environment, ownership, or rollout risk).
  • If a feature appears shipped but behavior is inconsistent, verify the current state in Platform changelog before changing implementation assumptions.
  • If dependencies collide (for example analytics and reliability work), prioritize work that lowers production risk first and re-sequence non-blocking enhancements.