Hacker News Reader

Ah, got it, thank you!

How does it work. In the sense that what does it provide the client side. Does the client get served pre-rendered interfaces of some sort?

Trying to figure it out as the Meta apps are very nice UX wise and maybe web technologies have come a long way to "feel native" hence i am in disbelief at the leaps and bounds being made.

Not super sure about how the internals work but iirc this is the flow:

- Eng writes Hack/Python code on backend with a view tag-ish

- Client has native components for NT and Blocks. The native component references tag-ish from above and pulls code / config

- The code / config returned from the backend gets translated into Litho/ComponentKit components (so native Android UI elements) and rendered

what is `tag-ish`? Having trouble googling it

Interesting! Thanks for the explanation!

Interesting, does it cross compile a hack based DSL to iOS and android?

Curious to hear more!