← Back to home
Comparison · Infra & APIs

inlabru vs microViz

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

Shared themes:r-package

inlabru vs microViz: at a glance

FeatureinlabrumicroViz
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationmicrobiome, ordination, phyloseq, maintenance
Last editorial update39m ago1h ago
WebsiteVisit →Visit →

What is inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

What is microViz?

Microbiome ordination and visualisation, in maintenance and keeping pace with vegan and ggplot2.

microViz provides visualisation and statistics for microbiome data built on phyloseq, including ordination exploration, distance-based dispersion analysis and composition plots. The release notes are pointer-style entries that name a pull request and link a comparison range rather than describing what changed, so most of what can be established from this feed is cadence and dependency pressure rather than substance. Version 0.13.1 is the exception, naming documentation work on dist_bdisp and its defaults relative to vegan's betadisper.

Read the full microViz trajectory →

inlabru vs microViz: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

M
microViz
INFRA · APIS
0.0

Microbiome ordination and visualisation, in maintenance and keeping pace with vegan and ggplot2.

◆ Current state

microViz provides visualisation and statistics for microbiome data built on phyloseq, including ordination exploration, distance-based dispersion analysis and composition plots. The release notes are pointer-style entries that name a pull request and link a comparison range rather than describing what changed, so most of what can be established from this feed is cadence and dependency pressure rather than substance. Version 0.13.1 is the exception, naming documentation work on dist_bdisp and its defaults relative to vegan's betadisper.

◆ Where it's heading

Read through the dependency mentions, the pattern is a package spending its releases absorbing changes in the ecosystem beneath it: vegan deprecating summary in favour of scores, cowplot warning under ggplot2 3.5, testthat declarations centralised, CI actions updated. Nothing in the window indicates new analytical capability, and the 0.13.0 minor bump that would be the place to look for it ships with no notes at all. The honest reading is a stable package under maintenance by a single maintainer.

◆ Prediction

Expect continued upkeep against phyloseq, vegan and ggplot2 changes rather than a feature programme. Because the notes do not describe their own contents, a substantive release here would be indistinguishable from a maintenance one in this feed, so the direction cannot be read from these entries alone.

Alternatives to inlabru and microViz

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 inlabru or microViz.

See all inlabru alternatives → · See all microViz alternatives →

Recent activity from inlabru and microViz

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agomicroVizmicroViz 0.13.1
  3. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  4. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  5. 6mo agomicroVizmicroViz 0.13.0
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agomicroVizmicroViz 0.12.7
  8. 1y agomicroVizmicroViz 0.12.6
  9. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  10. 1y agomicroVizmicroViz 0.12.5
  11. 2y agomicroVizmicroViz 0.12.4

Frequently asked questions

What is the difference between inlabru and microViz?

Both compete on the same themes — r-package — within Infra & APIs. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is inlabru better than microViz?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to inlabru?

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

What are the best alternatives to microViz?

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