Code Complete?
Well, I think I've finished the major functionality for Slowpoke. I can pull and categorize accounts and transactions from SimpleFIN, I can bucket and track those amounts via budgets, and I can secure the accounts via Google login authentication. I can also handle a multitude of banking, credit, mortgage, and investment accounts.
At this point, I'll be so bold as to say I'm in an alpha 1.0 release stage. It isn't something I'd turn over to users in bulk yet, but it's something I can use for my own purposes. So, what do I need to do to get it in beta?
- Clean up/add some categories for general usage.
- Add aggregated smart categorization. Much of my time in the last couple of weeks has been spent understanding embeddings and vector databases to make this functionality as painless as possible, while also being as robust as possible.
- Add more functionality to budgeting. Currently, all categories, including transfers, are included for all budgets. Transfers between accounts aren't really a budgetable category, and not all users want to see/use all categories.
- Improve historical viewing for roll-up displays. Users can easily see their individual transactions, but can't easily see aggregate views of their accounts, net worth, etc. farther than a year out.
- Fix the branding. Much of the site references the AI-generated name "Financial Sanctuary"
- An internal security audit.
- An internal accessibility audit.
- Ensure that unit test coverage and code conventions meet my preferred standards.
That's still a pretty significant chunk of work, but it's still feasible to add that functionality by my revised October 1 deadline. I don't think these features need to be implemented in order to meet my original definition of done, but they do need to be completed in order to meet the requirements I have for a general availability launch, which I'm hoping will coincide with the new year.
Until next time, my human and robot friends.
Comments
Post a Comment