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
Great work! Keep building OP!
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?
Did it help to be a non-profit?
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
The numbers and amounts used for account validations and adding it to be able to pull or push money . Should not be shown public..
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?
We should judge software by the quality, not by authors age.
It is a deliberate advertisement to VCs to find "the next Mark Zuckerberg" which the entire point is that there is only one.
For every 1,000+ startups there is exactly only *one* exceptional founder.
Be careful with this. If Apple finds out for instance, your app will still be taken down.
Interpreted code may be downloaded to an Application but only so long as such code: (a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application (b) does not bypass signing, sandbox, or other security features of the OS; and (c) for Applications distributed on the App Store, does not create a store or storefront for other Applications.
I do actually believe that zero teenagers should make banking apps or run non-profits.
its the controvertial takes that bring readership...
Click the date on the post, and if you have a button saying "vouch", click that.
That sounds like a lot of fun and should be a pretty social experience.
Also I'm going to assume his parents are proud, which should put his family at ease.