Airtable looks pretty interesting, and it looks extremely customizable. Thanks!

I'll see what I can do

Depends on the relationship between the designer and developer (i.e. contractor vs in-house). I've worked with both, and the handoffs (read: level of detail) are very different. You can usually get away with less when working with a team member and have a conversation since they should be familiar with how you do things if they aren't new, but with a contractor, more is always better.

Regardless, I always provide a Sketch file, PNGs of the designs & the different states, a project summary with descriptions of every interaction (these can get quite long, so I try to have sections w/ headings to make it easier to scan, and checklists with clear goals/outcomes), prototypes or examples of similar interactions if necessary, and of course all the assets they need. There are usually questions and changes along the way, but this tends to be enough to communicate the design/project goals, and then once a PR is submitted I will provide feedback or create issues if it won't block the release.

This looks closer to what I was looking for. I'll check it out, thanks!

Was the "free" plan Steve mentioned discontinued? I'm always willing to pay for a service, but this is quite expensive if you're not a business or expect a lot of traffic. Would you say GoSquared is more for businesses/larger sites then?

Fair enough. I think the main issue with the touch bar is that it makes so much sense for non-pro users (those who don't know that keyboard commands and shortcuts even exist), but it was introduced on a "pro" machine.

My point about the sizing is that in one app it might be 33%, but in another it could be 20% or 50%. Sure this might work for the left-most action in all apps, but for the rest you will have to looks down regardless. That is, unless you have an impeccable memory :P

The one concern I've seen come up again and again, and something I myself experience, is that you have to take your eyes off the screen to look at it before using it, unlike shortcuts on the keyboard where you only use muscle memory. To make matters worse, the buttons are tiny and require a good degree of precision to hit.

Your solution work because there are three options in each, but what happens when the system is showing more than three optiions? I assume they would scale like Safari tabs until there isn’t any more space (the size they are currently) and the user will still have to scroll/interact to see more options.

With that said, I’m surprised the larger buttons shown in your mocks aren't the default behavior, but I don’t think that will help with the issue you are describing. You don't have to look @ a keyboards because they are always fixed. But if you are switching apps all the time, your context changes as well. In one app the same button will be a tab switcher for a website, and in another that same tap area will create new message. No matter what, the user has to look down to see what that section of the tab bar is doing, regardless of the size of the UI.

The only app I know of that "smooths out shaky line-work" is Procreate. You can customize that setting on a per-brush basis. Not sure how that would work for wireframes though…

Personally I use Notes (and the digital ruler) for wireframes, OneNote for handwritten notes, and Linea for sketches.

If you working with very specific text elements (i.e. won't change), try converting it into an outline. Not ideal, but could help with alignment.

We use Github heavily, so all of the descriptions are stored in issues that we can reference later. We also try to create action items for each section of a description (i.e. the questions I mentioned earlier) using tasks - [ ] ……… that help to summarize what we expect to see once the PR is submitted. This way everyone is on the same page about what's been completed, and what's still WIP.

In terms of assigning people, Github handles that as well. You can assign the appropriate person/team to a particular issue, and so the right stakeholders are notified about the project. We also have tags that describe the status (i.e. In Progress, More Info Needed…, Priority Levels, etc).