I was a fan of Robinhood's mission of democratizing finance and prioritizing UX for casual traders. They seem to jump on every hype train though, crypto, prediction markets, now agentic trading, whether it is ethical or not or good for their customers or not, and it seems like the distance between "democratizing finance" and "finding new suckers" is closing. Disappointing but not surprising.
Robinhood's crypto offering is extremely deceptive. They offer "commission-free cryptocurrency trading" but don't make it clear that you pay a 0.95% fee[1] on every trade (technically a 'spread' and not a 'commission' but there is hardly a difference). They also take 25% of staking rewards. These are absurdly high fees.
yeah this is what author hints at with "Push as a battery problem". Apps are limited by default in what they can do in the background due to this, so most apps are in a suspended state not making network calls when you are not using them. To avoid the app having to keep running this stuff is delegated to OS which tells the app, "hey I have a push for you wake up and handle it!" You can send pushes locally but because of the background limitation it is not practical for unpredictable events like messages coming in.
Not sure i understand. Sure it doesn’t require it but Apple doesn’t trust you to handle it because you’ll probably drain the battery or spam the user or whatever, that is Apple MO, putting themselves in the middle so they can control the experience.
The single persistent connection is just to receive pushes, there is still some daemon controlled by apple in charged of dispatching to correct app.
hey now, they should be grateful they get enough tokens for their appointments with ClaudeMD for their statistically below par data labeling performance, we could reduce the allowance if we keep hearing that kind of talk. We have been very generous with portions at the automatic canteen as well, that energy could be better allocated to the maintenance bots in the server farm.
just this week i pushed back on some requirements in a very detailed product spec I was implementing to speed up time to ship. The pm had no idea what I was talking about because the requirements were invented by an LLM. This is not a bad PM, discipline doesn't scale.
a bit of a roundabout way to answer this, but i think most native devs are okay with a self contained app element using webkit, that is what it is there for and generally stuff like rendering html, markdown, a one off static page, it is just a view from UI perspective. When things get more interactive, have a navigation hierarchy, animations etc are when things start to diverge from native feel and performance and you have gone too far.
Just make it a semi-hidden multistep option like browsers when you visit a site with a bad cert, just annoying to leave what you are doing go to system settings and fiddle.
An author who lives in Portland but gets a mail-order coffee subscription from California, no less. A half-dozen indie microroasters within 2 miles of him? _Not good enough_
The entire Has Been album is a great work. I have many of the songs on rotation in my daily playlist. I'm very much looking forward to his heavy metal album which lands in a few months. Obviously also, this: https://www.youtube.com/watch?v=BdUMICxLXhM
reply