← Back to home
Comparison · Infra & APIs

FoReco vs Hotjar

A side-by-side editorial comparison of FoReco and Hotjar — release velocity, themes, recent moves, and the top alternatives to consider.

FoReco vs Hotjar: at a glance

FeatureFoRecoHotjar
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, hierarchical-reconciliation, time-series, s3-classesuser-research, session-replay, surveys, usability-testing
Last editorial update54m ago7d ago
WebsiteVisit →Visit →

What is FoReco?

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

Read the full FoReco trajectory →

What is Hotjar?

Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.

Hotjar's public update feed carries nothing newer than April 2025, and the entries it does carry arrive in duplicate pairs — a short stub and the full post, a few hours apart. What the archive shows is a product that spent 2024 and early 2025 expanding from passive observation (heatmaps, recordings) into active research: unmoderated User Tests, AI tagging of survey responses, and finally prototype testing.

Read the full Hotjar trajectory →

FoReco vs Hotjar: editorial side-by-side

F
FoReco
INFRA · APIS
0.0

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

◆ Current state

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

◆ Where it's heading

The package is completing a reversal it started in 1.0.0. That release simplified outputs to plain matrices and pushed metadata into attributes reachable via recoinfo(); 1.3.0 removed recoinfo() outright and put the structure back as a class with components(), summary(), and plot() methods. The direction is toward being infrastructure rather than a function library — the class is exported through new_foreco_class() and a sibling package has already adopted it. Method coverage has meanwhile broadened from optimal combination into non-negative algorithms, bounded reconciliation, and Gaussian and sample-based probabilistic variants.

◆ Prediction

The soft-deprecated res2matrix() is flagged for removal, so a subsequent release should finish that cleanup; with the class now exported, expect more methods to hang off foreco objects rather than more top-level functions.

Hotjar logo
Hotjar
INFRA · APIS
0.0

Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.

◆ Current state

Hotjar's public update feed carries nothing newer than April 2025, and the entries it does carry arrive in duplicate pairs — a short stub and the full post, a few hours apart. What the archive shows is a product that spent 2024 and early 2025 expanding from passive observation (heatmaps, recordings) into active research: unmoderated User Tests, AI tagging of survey responses, and finally prototype testing.

◆ Where it's heading

The direction visible in these entries is a move up the research stack — from watching what users did on a live site toward asking them questions and testing designs before they ship. User Tests removed the moderator, AI tagging removed the manual sorting of open-ended responses, and prototype testing removed the requirement that the thing being tested exist yet. Each step cut a person out of the research loop. Whether that arc continued past April 2025 is not something this feed can answer.

◆ Prediction

No prediction is supportable from these entries. The feed has published nothing for over a year, so any claim about Hotjar's current direction would be invented rather than observed — the only honest read is that this channel has been abandoned or moved elsewhere.

Alternatives to FoReco and Hotjar

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either FoReco or Hotjar.

See all FoReco alternatives → · See all Hotjar alternatives →

Recent activity from FoReco and Hotjar

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoFoRecoStrict argument validation and a pruned help index
  2. 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object
  3. 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
  4. 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
  5. 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
  6. 1y agoHotjarDuplicate stub of the April 2025 Surveys and User Tests post
  7. 1y agoHotjarPrototype testing extends User Tests to designs that do not exist yet
  8. 1y agoHotjarDuplicate stub of the User Tests launch post
  9. 1y agoHotjarUnmoderated User Tests bring usability testing in-product
  10. 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions
  11. 2y agoHotjarAutomatically tag survey responses
  12. 2y agoHotjarCustomize the button labels in Surveys

Frequently asked questions

What is the difference between FoReco and Hotjar?

They serve adjacent needs but don't currently overlap on shipped themes. FoReco and Hotjar are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is FoReco better than Hotjar?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and Hotjar are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to FoReco?

Top FoReco alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoReco alternatives" section above for the current picks, or visit /alternatives/foreco for the full list with editorial commentary on each.

What are the best alternatives to Hotjar?

Top Hotjar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hotjar alternatives" section above for the current picks, or visit /alternatives/hotjar for the full list with editorial commentary on each.