sbfriends

Australia's consumer guarantees cannot be replaced or excluded by warranties and offer huge protections for consumers who know how to exercise their rights. Companies try to apply friction to the process and I suspect that frustrates a lot of people to the point of giving up.

I think once you grok sagas, they're very difficult to replace. I think it's such a neat mental model to be able to dispatch global actions and having async tasks able to respond. I think it leads to nicer decoupling in components between UI & data.

Your site doesn't render anything without JS enabled :'(

> Why did you choose to use React Native if you weren't planning to use it for cross-platform purposes out of the box? Why not use swift or objective-c and then port to Android if there's customer demand?

There's lots of reasons someone might want to start with Expo while developing an app. If their team doesn't have native experience, it's far more accessible than needing to maintain a native stack (or two should they support Android).

It also supports the ability for OTAs out of the box, which allows them to be responsive to feedback / bugs / feature requests.

There's more to RN/Expo than "do you plan on releasing a cross-platform product at once". Even if their road map is "Apple now, Android later" the decision would still be justified.

Maybe not platform per se, but through your domain. There's a huge power in that (as gatekeeper of content). It means department's have no choice but to adhere to the standards and recommendations.

The exemplar projects in the Australian system were discontinued after the second round, and were really just lip-service -- at the end of the day, even the exemplar projects were at the mercy of internal Departmental IT operations who ultimately decided what went on to their Departmental domains.

Australia tried to follow this with gov.au, and it was a bit of a debacle. It ultimately didn't work because it the agency driving it lacked a stick and couldn't coerce agencies to give up their branding/content. Agencies couldn't see the financial incentive -- they'd have to give up their funding and control, and that just wasn't appealing at all.

Frustratingly the idea will be dead for a good time to come now. For an agency to do this, they need a stick -- I believe the GDS had IT spending levers they could pull to control how money was spent across the entire public sector. This made them quite powerful and ultimately allowed them to say "if you want to publish your agency's content, it has to be on our platform".

The end result is a far better UX.

Absolutely nothing renders without JS FYI :( noscript is simple to add, at least warning users it's required.