← Back to home
Comparison · Infra & APIs

afcharts vs inlabru

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

afcharts vs inlabru: at a glance

Featureafchartsinlabru
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesdata-visualisation, government-statistics, ggplot2, colour-palettesbayesian-modelling, spatial-statistics, r-package, api-consolidation
Last editorial update1h ago47m ago
WebsiteVisit →Visit →

What is afcharts?

UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.

afcharts supplies the UK Analysis Function's chart styling for ggplot2, as a theme, colour and fill scales, and a use_afcharts() call that applies the styling globally. Version 0.5.1 extends the sequential palette to five shades so it can carry quintile data such as deprivation bands, renames the na_colour argument to na.value, and adds a reset argument to switch the styling back off. The package began as a first release derived from sgplot and has had three releases in roughly two years.

Read the full afcharts trajectory →

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 →

afcharts vs inlabru: editorial side-by-side

A
afcharts
INFRA · APIS
0.0

UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.

◆ Current state

afcharts supplies the UK Analysis Function's chart styling for ggplot2, as a theme, colour and fill scales, and a use_afcharts() call that applies the styling globally. Version 0.5.1 extends the sequential palette to five shades so it can carry quintile data such as deprivation bands, renames the na_colour argument to na.value, and adds a reset argument to switch the styling back off. The package began as a first release derived from sgplot and has had three releases in roughly two years.

◆ Where it's heading

The work splits between palette design and keeping the styling composable. On the design side the sequential palette growing to five shades is driven by a specific reporting need rather than aesthetics, since quintiles are a standard unit in UK official statistics. On the mechanical side, the na.value rename was forced by ggplot2 v4.0.1, theme_af() now respects options set by an earlier use_afcharts() call, and a reset argument acknowledges that global styling needs an off switch. These are the problems a styling package hits once people use it inside larger documents.

◆ Prediction

Expect continued adjustment to ggplot2 v4, since the na.value rename is unlikely to be the only argument affected, and further palette work driven by the reporting formats government analysts actually publish. As a sibling to aftables in the same Analysis Function family, it is likely to keep tracking that guidance rather than setting its own direction.

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.

Alternatives to afcharts and inlabru

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

See all afcharts alternatives → · See all inlabru alternatives →

Recent activity from afcharts and inlabru

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  4. 5mo agoafchartsSequential palette reaches five shades for quintile data
  5. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  6. 1y agoafchartsNamespace and argument-passing fixes
  7. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  8. 1y agoafchartsFirst release, derived from sgplot

Frequently asked questions

What is the difference between afcharts and inlabru?

They serve adjacent needs but don't currently overlap on shipped themes. 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 afcharts better than inlabru?

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 afcharts?

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

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.