سجل التغييرات

Site visits are where location decisions get made, so MapDove now comes with you.

• iOS and Android. One app, built with Expo, that signs in with your existing MapDove account and respects your organization’s plan and seats.
• Site check. Standing at a candidate location, run a Site check for your current position, powered by the same MapDove API and models as the web app.

The mobile app is rolling out now. As with the web app, all figures come from the synthetic demo dataset unless your organization has custom data feeds.

MapDove is now generally available. Version 1.0 rounds out the platform with the features teams asked for most during the beta.

• Alerts. Watch a place’s visits, visitors or dwell time and choose a direction (up, down or either) and a percentage threshold. An alert triggers when the latest 7 days of data differ from the weekly average of the 28 days before by more than the threshold. Alerts are included from the Pro plan (10 on Pro, 100 on Business).
• Projects. Save any analysis (suitability, Huff forecast, catchments, compare sites) with its parameters, results and notes, and reopen it later exactly as you left it.
• Audit log. Org owners and admins can review sign-ups and sign-ins (including failed sign-ins), password and two-factor changes, members added and removed, organization updates, API keys created and revoked, checkouts and plan changes, projects created and deleted, alerts created and CSV exports.
• Two-factor authentication. Protect accounts with authenticator-app codes, set up in a minute from your profile.

Plans start with Free at $0, then Pro at $149/month and Business at $499/month, with Enterprise available on request. See pricing.

Thank you to every beta team who shaped this release.

MapDove now speaks three languages. Arabic joins English and Spanish across the app, the marketing site and the documentation.

Right-to-left done properly

• Navigation, panels, tables and charts mirror correctly in RTL, while maps, coordinates and numeric axes keep their natural orientation.
• Numbers, currency (AED and USD) and dates format according to the selected locale.
• Mixed-direction text, such as English brand names inside Arabic sentences, renders cleanly.

Four themes

Choose between Light, Dark, Midnight and Sand in Settings, or follow your system setting. Every theme applies to the map basemap, choropleths and charts, not just the chrome, and Sand offers a warm, low-glare palette for long analysis sessions.

Your language and theme follow you across devices. Switch language from the footer or your profile.

Catchments now support three units: kilometers, miles and drive minutes. Request up to four rings per analysis, such as 5, 10, 15 and 20 minutes, from the map or the /sdss/catchment endpoint.

How it works: drive-time rings convert minutes to a radius using each city’s average travel speed (Austin 42 km/h, Houston 45, Phoenix 50, Miami 35, Dubai 55). This is a transparent, speed-based approximation, not a road-network isochrone, so it scales catchments sensibly between markets but won’t bend around rivers or follow freeway corridors. Demographics inside each ring are area-weighted from the hex grid.

The catchment panel shows the equivalent radius for every drive-time ring so you always know what you’re looking at.

For guidance on choosing between units, read Drive-time vs. radius catchments and the catchment docs.

This release focuses on getting the basics of API access right.

• Organization API keys. Owners and admins create named keys in Settings. The full secret is shown once at creation; afterwards only a short prefix is displayed, so keys are easy to identify without exposing them. Only a hash of each secret is stored.
• Revocation. Revoking a key takes effect on the next request, because every request is checked against the list of active keys.
• Last used. Each key shows when it was last used, so stale integrations are easy to spot and clean up.
• Usage dashboard. Settings shows current-month analyses, API calls and exports against your plan limits, with a six-month history.
• Clearer limits. Requests over a monthly limit return 402 plan_limit with a message naming the limit that was reached.
• General reliability improvements to key management and usage counting.

API access is available on Pro and above. See plans and limits.

Shortlists rarely have one candidate. Compare sites puts up to five locations side by side in a single view so the trade-offs are visible at a glance.

For each candidate you get:

• Suitability score and the underlying MCDA criteria, using the same weights for every site so the comparison is fair.
• Huff forecast of annualized expected visits and market share.
• A standard catchment of 1 mile in US cities or 1.6 km in Dubai, with area-weighted population, households and income.

Drop pins on the map or paste coordinates, label each site, and adjust weights to see how the ranking shifts. Results can be saved as a project and are available through the new /sdss/compare-sites endpoint.

Read more in the compare sites docs.

The Huff gravity-model forecast now answers the question every network planner asks next: how much of this new store’s traffic comes from my other stores?

When you run a forecast for a branded site, MapDove identifies your brand’s existing locations in the same category and city, and reports:

• Gross expected visits for the candidate site, annualized.
• Cannibalized visits per existing location, with the share of each store’s modeled demand that shifts to the new site.
• Net new visits to the brand, after cannibalization.

The trade-area map highlights hexes where the candidate and existing stores compete, so you can see where the overlap sits. Cannibalization results are included in the /sdss/huff API response and in saved projects.

See the cannibalization docs for the method and its assumptions.

MapDove now ships five demo cities. Dubai joins Austin, Houston, Phoenix and Miami with 16 neighborhoods, 247 places across all 14 categories and a full year of daily visits, from the Downtown and DIFC core along Sheikh Zayed Road to Deira, Dubai Marina and the master-planned communities inland.

What’s included:

• Local units and currency. Areas, distances and catchments display in metric units, and incomes in AED. US cities keep imperial units and USD.
• A Dubai-specific season. The city’s visit model peaks in mid-January with the strongest seasonal swing in the dataset (about ±15%), reflecting the cool-season pattern.
• Full SDSS coverage. Suitability scoring, Huff forecasts, trade areas and cross-shopping all work in Dubai from day one.

As with every city, Dubai data is a synthetic demo dataset modeled from neighborhood-level parameters. Read the market note for a guided tour.