has put together a walkthrough of how he presents emergency exits to users ("forced move") in Arké. He's a master of user-friendly bitcoin UX, so there are valuable tips for anyone building Bark into their app. https://www.youtube.com/watch?v=GxW574iolr4

We've been doing some research on client-side Lightning pathfinding for Bark wallet apps. Instead of the Ark server working out the best payment route on the user's behalf, the wallet app builds the route and the payment onion itself, so the destination is not shared with the server and potentially eliminating minimum fees on Lightning transactions. Full findings, link to proof of concept, and areas for further research: https://blog.second.tech/bark-client-side-pathfinding/

Bark 0.4.0 is out, and receiving just got simpler: one BIP 321 payment request covers Ark, Lightning, and on-chain, built in a single barkd call or straight from the SDK. Also in this release: fee quotes for on-chain payments before you send, wallet notifications without a websocket, control over exactly which VTXOs a payment spends, and crash safety across every payment operation. Full changelog: https://second.tech/docs/changelog