Show HN: HCB Mobile – financial app built by 17 y/o, processing $6M/month (hackclub.com)
One of my biggest challenges, while juggling being a full-time student, was getting permission from Apple/Google to use advanced native features such as Tap to Pay (for in-person donations) and Push Provisioning (for adding your card to your digital wallet). It was months of back-and-forth emails, test case recordings, and also compliance checks.
Even after securing Apple/Google’s permission, any minor fix required publishing a new build, which was time-consuming. After dealing with this for a while, I adopted the idea of “over the air updates” using Expo’s EAS update service. This allowed me to remotely trigger updates without needing a new app build.
The 250 hours I spent building this app were an INSANE learning experience, but it was also a whole lot of fun. Give the app a try, and I’d love any feedback you have on it!
btw, back in March, we open-sourced this nonprofit neobank on GitHub. https://news.ycombinator.com/item?id=43519802
23 comments
[ 2.5 ms ] story [ 44.3 ms ] threadWe should judge software by the quality, not by authors age.
Did it help to be a non-profit?
Great work! Keep building OP!
OpenAI’s executive claiming - made one of the top visited websites :-)
I'm curious whether you were able to build the app using backend APIs that were already built, or whether building this app created new requirements for those APIs?
Be careful with this. If Apple finds out for instance, your app will still be taken down.
https://github.com/hackclub/hcb
Excellent work on the mobile app though I would wonder, since HCB runs on Hotwire, why it was not written as a Hotwire Native app which would leverage the existing Rails Hotwire app and not require a complete rewrite?
I get that you want to be "open", but is everyone involved in these transactions ok with them being shared? Even if they are, this doesn't seem like a good idea security wise. I see partial account numbers and other IDs/numbers that I assume you'd prefer not be public, regardless of how insensitive they may seem now.
EXPENSIFY, INC. VALIDATION XXXXXX5987 THE HACK FOUNDATION +$0.89
FRONTING $10,000 TO CHRIS WALKER FOR GITHUB GRANTS MADE FROM PERSONAL ACCOUNT -$10,000.00
CHECK TO LACHLAN CAMPBELL +$800.00
Transfer to Emma's Earnings -$1,923.08
Given how famed HN is for its pedantry I thought you may find this useful as sooner or later someone in your industry might make a judgement on it.
MM is million, BTW.
also a simple google search disproves what you are saying. M is correct
https://news.ycombinator.com/newsguidelines.html
How are you ensuring the application will remain maintainable in the future, you are not breaking existing stuff and integration with the actual platform is always up-to-date?
In short, what's the testing strategy for something that claims to deal with $6M a month?
If there is none, you likely want to read up a bit on things like Testing Pyramid, automated test strategies (unit-, integration- and end-to-end testing).