Nativestarter

Changelog

Changelog

Entries are added when something ships, not when it is planned.

  1. Shipped

    The whole Bluesky app is ported

    All 78 Bluesky screens now exist in SwiftUI and Jetpack Compose, including sign-in, the composer, chat, moderation and search, with 1,487 iOS tests and 1,315 Android tests. The checkpoint plan of 127 checkpoints was accepted on 22 October. Built is not verified: three screens are measured in full, and a parity sweep that compares every screen against the React Native app is running on both platforms. Six checkpoints have passed every gate; the rest are counted when theirs do.

  2. Changed

    The advisory call is free

    The 60-minute advisory call with the founder no longer has a price. Readiness Reports and pilots are now requested by email and scoped before any work starts, so the Pack-owner discount on support is gone. The Pack licences are the only prices on the site.

  3. Fixed

    assess-rn-app measures the screen a route renders, not the route file

    Screen complexity came from the route file's line count. An expo-router route file is glue, so every screen in an expo-router app scored simple and the estimate came out roughly a third low. The analyzer now follows the route to the component, a connect-style barrel to the component it wraps, and a route that only re-exports its screen to wherever that screen lives. On a 227,000-line app the estimate moved from 209 engineer-days to 341. React Navigation apps are unaffected. If you ran an assessment on an expo-router app before today, re-run it: the number changed.

  4. Changed

    Pay once, updates forever, on every licence

    The licence and the terms always said all future updates were included; the pricing page said twelve months. The licence wins and the pricing page was wrong. Every tier now includes every future update of the Pack for as long as it exists, with no renewal and nothing to re-buy. A licence is delivered as an invitation to a private repository, one per seat, and a seat is one developer with an email address at the licensed company.

  5. Shipped

    The Bluesky migration is published, with its drift and its open defect

    Three screens of the Bluesky app, ported to SwiftUI and Jetpack Compose and measured against the running React Native app: 35 screen states, no screen above the 2% gate, 26 of them drift rather than a pass and accepted in writing on 22 October. The worst screen is 1.94%. One functional defect is open and published as open: swipe back does not pop the thread on iOS. Both port repositories are public.

  6. Shipped

    check-parity no longer needs ImageMagick, and three pages say what the Pack does not do

    The parity pipeline ships its own screenshot comparator, which reports structure, position and content separately and needs nothing else installed. ImageMagick is now optional and used only by the older pixel-diff script. Three new pages state the limits: what parity means and the six things it does not check, how the Pack runs and what happens when a checkpoint fails, and what the assessment has actually been run against.

  7. Announced

    The Migration Pack becomes the main product

    The Pack is now sold in three licences: Individual, Team and Company, each a one-time payment that includes every future update of the Pack, forever. Readiness Reports, advisory calls and pilots continue as optional support, with 20% off for Pack owners. A showcase migration of Bluesky was announced.

  8. Shipped

    Readiness Reports and the Bluesky sample

    Readiness Reports opened. The first public sample reads Bluesky's open-source app and recommends a targeted move rather than a rewrite. The Migration Pack's first skill, assess-rn-app, produced its inventory.

  9. Announced

    Nativestarter becomes a migration practice

    The site now offers help moving React Native apps to SwiftUI and Jetpack Compose. The Migration Pack is in development.

Before this, Nativestarter was a React Native boilerplate. It never launched and nobody bought it. We retired it when the question teams were asking changed from how to start on React Native to whether to leave it.