{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig6ilo56tkehxkp5v5up25tyjaubkuakn2dd2h3t2t2fsmifohnhi",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjyiu3654u62"
  },
  "path": "/t/hatter-native-haskell-mobile-apps/13952#post_9",
  "publishedAt": "2026-04-21T06:14:52.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "harryprayiv:\n\n> I’m not going to write it off just for that\n\nDepends.\n\nI don’t know if OP has any credibility in that domain and whether this whole thing just works by accident (or at all).\n\nIt also happens that vibe coded projects are discarded/abandoned quickly, because maintaining something long term and being engaged in a project is something entirely different than a weekend claude session.\n\nAdditionally, mobile apps are end-user facing and there’s lots of concerns wrt **privacy and security**. And we know those properties don’t magically appear out of thin air and that vibe coded projects are often more vulnerable.\n\nThat means to me that someone announcing a vibe coded mobile app framework has more convincing to do than is visible here. Otherwise I’m not sure how seriously I can take this.",
  "title": "Hatter: Native Haskell mobile apps"
}