diveintothe9

I'm from South India, and in general, people's names fall into sets of common given names and common family names, but it can get tricky. Things vary state-to-state, and even within states, across castes and subcultures. However, this also makes it somewhat easier to gauge where someone is from. Over time, you recognize some name patterns and you can guess that they're from a specific place, speak a specific language, etc.

For a very generic example, if I encounter someone with the surname "Singh", I'm reasonably sure they're from the northern states, and likely speak Hindi apart from their native tongue. Also in terms of identifying someone's given name, they're usually from a broadly known pool. As an analogue to western names, if someone says their name is James or Marie, you're mostly guessing that's their given name, even though it's possible to have those as last names as well (eg. LeBron).

Agreed, data volumes are definitely the biggest hurdle in this scenario. Any of the cloud DAWs I've seen mostly offer basic features, and a handful of recording tracks at best.

Just checked out Ardour, looks great! Being able to work with videos and (I presume) work on additional audio and eventually mix the two audio sources back into the video is a fantastic feature.

The only function I've added to my touch bar that wasn't previously available was Screenshot, because I do a lot of snapshotting and screen recording, and I'd rather hit that than the stupid Siri button.

I wish there was a way to add custom app-specific shortcuts to the touch bar (maybe there is? I'm not sure). I use Sketch a lot for designing, and I'd love to have access to my document colors and text styles in the touch bar, but no joy.

I'm guessing this is different from a DAW? Also, cloud-based music making applications is an area I'm generally interested in, and I find it somewhat crazy that a lot of mainstream music software companies haven't stuck a foot in. I'm aware of some, like Cubase having cloud collaboration, but it's mostly blue ocean.

Amateur product designer here, I'm really interested in what you would consider to be first principles when it comes to expected appearance/behavior/functionality of a phone, especially nowadays when the "phone" part of such a device/interface is almost an afterthought.

I'm also interested to hear what you think are the shortcomings or limitations of our current idea of a (smart)phone interface.

I'm a UX designer, and by no means a pro, but my workflow is usually along the lines of:

- wireframe on Sketch (some people are faster on paper, I'm faster on Sketch/XD/whatever)

- create what I call a medium-fidelity mockup (basic styling, all components, etc, but not much actual content)

- create a small PWA/webpage to demonstrate behavior and flow

- go back and complete my high-fidelity design

- send it, and any styleguides, to the devs

Throughout these steps there are multiple rounds of iteration, review, and branching, but eventually you have a product design ready to go.

Point 6 would be such an amazing achievement to hit, even if adoption isn't widespread immediately.

I like the idea of a split view, so you can continue browsing frontpage/possibly a subreddit while still looking at a comment section.

If there was a way to incorporate mod controls and refresh just for the right pane, this would be a GODSEND for monitoring active threads.