Original Summary

I'm the maker of Jalsseum, a Korean expense-tracking app I'm building with AI as a non-developer. I wanted to keep personal spending separate from shared household expenses. One lesson was surprisingly small: testing one successful paste wasn't enough. In a set of 22 synthetic payment-message examples, an earlier parser failed 11. After fixing the parsing rules, all 22 passed that test set. That is not a real-world recognition rate. A later issue was preserving an edited amount and selection when adding another message; that flow was also improved. Imported amounts, dates and descriptions still need review before saving. There is no automatic bank connection. The app has personal/shared ledgers and invitations with read-only or editing roles. The screenshots on the site use fictional example data. As of October 18, the iOS and Android submissions are under review; this is not a public-download launch. The site has real app screens and a short demo, not an ungated working web app. Build notes and demo: https://yunseokl.github.io/jalsseum/news.html#message-lessons When testing an import flow, what second action has caught a bug that the first successful action missed?   submitted by   /u/lys1108 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/18 13:53:01