v0.9.8

The tablet half of the sd-phone ecosystem: the same apps, the same accounts and the same data, laid
out for a screen you hold in two hands rather than one.

This is the first packaged release of sd-tablet, and it starts at 0.9.8 rather than 0.1.0 on
purpose. The tablet has no UI source of its own: it builds from sd-phone's, and the release workflow
checks the phone out at the same tag it is building. The two version numbers are therefore one
version number, and a tablet zip is only ever the phone's UI in a different chassis.

Read this first

1. sd-tablet requires sd-phone at the matching version. Install sd-phone v0.9.8 alongside it.
   A tablet paired with a different phone release is not a supported combination.
2. This is where the MDT lives. The three terminals run on both devices as of 0.9.8, but they
   stay hidden everywhere until you set Enabled = true in sd-phone's configs/mdt.lua.
3. Props are a separate resource. sd-tablet-props ships the model and its eight colourways.

What it is

• Every server-backed app the phone has, re-laid out for the tablet: multi-column browsing, a
  persistent sidebar where the phone pushes one page at a time, and detail beside list rather than
  detail replacing list.
• One account, one dataset. Messages, mail, social feeds, banking and everything else are the same
  rows the phone reads; the device is a viewport, not a second identity.
• Device-scoped settings. Appearance, wallpaper, density and layout are remembered per device, so a
  phone and a tablet each keep their own look without fighting each other.
• Racing and the three MDT terminals, both of which are laid out for this screen first and
  fold down to the phone rather than the other way round.
• Home screen density presets, matching the phone's.

Install

1. Install sd-phone v0.9.8 first.
2. Drop sd-tablet into your resources folder and ensure it after sd-phone.
3. Add sd-tablet-props if you want the in-hand model.

Under the hood

The release zip is a drop-in resource folder: fxmanifest, client, server, configs, locales, images
and the built NUI, with no source and no dev config. The packaging step fails the build if
fxmanifest.lua declares a path the staged resource does not contain, which is the check that stops
a release shipping without a directory it needs.