Not sure how it is in engineering, but some design/architecture professors tear up your work in front of you during a critique if it’s not good. It’s tough, but it teaches you to not get too attached and push for better. You need to care and feel attached, but also be able to look at it from a distance and let go quickly.

New version of Arké is on TestFlight. Transaction details are now a swipeable stack of cards to quickly flip through and add notes. Plus force move (unilateral exit) refinements, security hardening and bark package updates. Check it out. Share your feedback.

Update on stuff I worked on in the last month, which was primarily unilateral exit UX for Arké. It's coming along nicely. https://gbks.substack.com/p/security

Just had to think of this mockup I made 3 years ago about escalating security reminders. A wallet starts annoying you hardcore if you store more bitcoin in it than is appropriate for the security it provides...

Oh boy….

Just came across this design I made 1.5 years go for the core app to inform users about pending network updates (all made-up content of course).

I am with Ben Shneiderman on direct manipulation. https://www.youtube.com/watch?v=CWgPe8VjTsM

Prototyping a way to go more quickly through transactions and add details. What do you make of this stacked-card concept? https://youtu.be/tCVOI7dGt7Y

Interesting to see the term "Design Engineer" become more used. In 2004, when I first started working for digital agencies, before the term UX existed, the field was "Interaction Design", and todays "Design Engineer" was the "Interactive Developer".

The agency I worked at had technical architects, backend developers, application developers, interactive developers, designers, and PMs and I always thought this split-up made a lot of sense. It becomes very clear when working directly with people who are really good in their areas.

In more recent years, the idea of the full-stack developer was around, assuming that one person can just do it all, which never made much sense to me.

No matter what labels you use, building good software (or anything really) requires various skillsets.

There might be more effort going into making bitcoin usable by agents than by humans.

And another Arké release is up on TestFlight:
- Many improvements to force moves (unilateral exits)
- Tag and contact editor revision
- Settings - reorder and new Notification and Address Pattern views
- X-ray iteration (remove balance, change VTXO list to graph)
- Use real fee rates
- Minor revision of the intro videos