Flip responsive mode
Shipped v4.2.55. A third option beyond cards and horizontal scroll: at the breakpoint, the first column becomes a persistent row label and other columns flow inline.
Read 4.2.x roundupRoadmap
No fake quarters. No "coming soon" badges that mean nothing. Each item below has a real state: Now (shipped in the current 4.2.55 stable), Next (in active development for 4.3, mostly behind feature flags in nightly), Soon (queued for 4.4 once 4.3 lands), Later (researching).
4.2.55 stable
Shipped v4.2.55. A third option beyond cards and horizontal scroll: at the breakpoint, the first column becomes a persistent row label and other columns flow inline.
Read 4.2.x roundupShipped v4.2.54. Cap a table to its top entries by any column server-side, so search/pagination/export all respect the slice. Combined with group_by for management dashboards.
Read 4.2.x roundupShipped v4.1.60 / v4.1.61. First-class block and widget; same render path as the shortcode, full live preview in the editor.
Read embed sprintShipped v4.1.30. Map 4 GF fields onto WC product attributes, click cart icon, draft product created. WC-active conditional.
Read WC + hooksShipped v4.1.23 + v4.1.26. [gravity_chart] (bar / donut / 5 aggregations, zero-JS SVG) and [gravity_map] (Leaflet markers, no API key).
Read charts + mapsShipped v4.1.28. CSV exports stream in 500-row chunks, so 25k+ row exports complete on shared hosting without OOM.
Read bulk-data flow4.3 line, in active development
Render-only-visible row engine for cases past the 50k pagination ceiling. Sub-2-second load with under 50 MB heap. Currently behind a feature flag in nightly.
For exports that genuinely need 60+ seconds. Job-based pattern: start → poll → download URL. Targets the cases that hit PHP max_execution_time even with streaming.
XLSX and PDF currently buffer in memory; the 4.3 implementation chunks XLSX writes via PhpSpreadsheet's row-iterator API. PDF is harder; will likely defer to 4.4.
For [gravity_map] views with 1,000+ markers. Pure CSS / SVG approach where possible; falls back to a Leaflet plugin when not.
Google-Docs-style cell ownership when multiple users edit the same table at once. Behind a feature flag in nightly.
Native Postgres support for tables backed by external SQL sources (sister-product TableCrafter territory). Behind a feature flag.
4.4 candidates
For 5k+ row imports on sites with heavy downstream notification hooks. Configurable batch size + delay between batches.
Compare this month to last month. Quarter to quarter. Automatic delta + percent change cells.
Opt-in. Privacy-respecting. Off by default. Helps us catch the bugs customers do not bother to email about.
For CRM and event-management workflows: one form that holds multiple pipelines (e.g. demo-request vs support-inquiry, or main-stage vs workshop-track). Without forcing duplicate forms.
Machine-readable export of the debug log for programmatic ingestion (Datadog, Loki, etc).
Researching
REST is shipped (`/wp-json/gt/v1/`); GraphQL is the obvious next step for non-WordPress front-ends that prefer typed queries.
Native FluentCRM / Brevo / Mailchimp wiring for status-driven automations. Currently solvable in ~15 lines via the lifecycle hook; making it a 0-line settings panel.
Optional layer for summarising long-form fields, classifying free-text submissions, etc. Bring-your-own API key. Off by default.
For tables with date-typed columns. Calendar-shaped surface alongside the existing table / chart / map views.
Public roadmaps are usually fiction, vague timelines, items that vanish quietly, "Q3 2025" labels that mean "maybe next year". This one is structured differently. Items in Now already exist, click through to read the release notes. Items in Next are in active development, expect them in the next minor release. Items in Soon have specs but no code yet. Items in Later are open questions we are researching, they may move forward, may shift, may be killed.
If you want to influence what lands when, the most effective channel is email. Customer requests with concrete use cases jump the queue, that is how the totals row, auto-recalc, and per-user filtering all became real features.
Email roadmap inputReady when you are
10 days of full Pro access. If it doesn't pay for itself in the first week, you don't have to keep it.