Also Zube is fast :)
You can see our focus on developers by the layout of our board, which is more scrum style than kanban. Each developer has their own row. It makes it easy to see exactly what your tasks are. You can also assign issues by dragging the card over to the user's row, something that isn't possible with a kanban board like ZenHub. We care less about getting an overview of the whole project (what PMs care about) and more about what needs to be done (what devs care about)
We'll continue adding features that make developers happy whether they would fit into the GitHub Issues paradigm or not.
Comments - syntax highlighting; @mentions, emojis, issue reference autocomplete; live updating from GitHub comments for things like comment updates and deletes (so your data is consistent)
Cards - Commit references, events, and card references. Consistency of data, especially when multiple users are moving cards at the same time.
Boards - add and remove users from the board
Labels - create, update, and delete labels from a repo (not just a card)
Milestones - create, update, and delete labels from a repo (not just a card)
Zube also has many UX features that differ from Waffle like each user having their own row. Creating cards in any row/column. Dedicated views for each milestone.
Waffle has some features that Zube doesn't support right now like burndown charts and search. I'm not an expert on Waffle or anything so please correct me if I'm in error. It's kinda hard to know everything that a competitor does.
We've had the request for multiple repos on one Zube board when talking with PMs and consulting firms and we're aware that it's important for them. However, we're laser focused on making developers happy and they've told us that they care more about managing issues for a single repository, so we implemented that first.