TfTHacker on Nostr: npub16nhe0…vtnnq This is very well put. What I’m trying to encourage here is that ...

npub16nhe0zge4j7pceqakxenjtapnlrcdgg8pcx3fzthp82cj0cpnqtqzvtnnq (npub16nh…tnnq) This is very well put. What I’m trying to encourage here is that both the desktop, Web, and mobile should be developed in parallel so that the underline data structures & API’s can accommodate these different user paradigms. The problem is when you later try to tack one of these on there can often be missing elements. Sadly, many companies have to do a significant reactor to make mobile work well because the API don’t include the unique features that are needed or don’t scale.