Docs

PostHog Foldable iPhone Posture Tracking

Track foldable iPhone posture with PostHog's $hinge_status property. See which fold states drive engagement, drop-off and layout problems.

Engagement

A foldable device is not one screen size. It is several, and the user can change between them mid-session. If your analytics treats every iPhone as a fixed rectangle, you cannot tell whether a drop-off happened because the content was poor or because the layout broke the moment the device was opened.

On 2 October 2026, PostHog’s changelog added a $hinge_status property to foldable iPhone events, reporting whether the device is closed, partially open or fully open. For product teams preparing for foldable Apple hardware, that is the missing dimension for segmenting behaviour by posture.

Without it, you end up averaging very different experiences together. A checkout that converts well on a fully open display and badly on a closed one will look merely average.

Data Points to Track

  • $hinge_status: closed, partially open or fully open, on every event
  • posture_change_count: how often the fold state changes within a session
  • screen_name and screen_size_class: which screen was showing, and its size class at the time
  • layout_variant: which layout your app rendered (compact, adaptive, two-pane)
  • conversion_event: key actions such as sign-up, purchase and task completion
  • time_in_posture_seconds: time spent in each fold state per session
  • app_version and os_version: to separate layout bugs from platform behaviour

Setup Steps

  1. Update the PostHog iOS SDK to the release that includes the foldable posture property.
  2. Check that $hinge_status appears on events from a foldable test device or simulator before shipping.
  3. Create a breakdown of your core funnel by $hinge_status in your analytics tool.
  4. Add a custom event such as posture_changed with previous and new state, so you can see transitions, not only snapshots.
  5. Record the layout variant you rendered so layout and posture can be analysed together.
  6. Set a minimum sample size before acting on results, since foldable traffic starts small.

Actionable Insights

If conversion differs sharply between fold states, you have a layout or content problem in the weaker state. Start with the screens where the gap is widest.

A high posture change count on one screen suggests users are opening the device to see more. That is a signal to offer a richer two-pane layout there.

If sessions that start closed and end open show higher engagement, design the transition so state, scroll position and form input survive the change. Lost input after a fold is a quiet cause of abandonment.

Treat early foldable data as directional. The volume will be small, so use it to prioritise testing rather than to make final decisions.

It also helps to agree a shared vocabulary early. Decide what “partially open” means for your product, for example tent or laptop style use, and document how each state maps to a layout. Product, design and engineering can then read the same dashboard and reach the same conclusion, instead of debating what a segment represents after the data arrives.

Finally, keep a short test matrix of your top five journeys across all three fold states. Re-run it every release. Analytics will tell you when something is wrong, but a simple repeatable test catches layout regressions before users do.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert