1. They are located next to the other actions rather than Alllll they way to the right of a view.... 

The buttons become tedious to use when you have many columns in a view. Sometimes they remain completely off the page on the x axis so you have to scroll to the right. 

Let's get some Fitt's Law love and have you guys give us the option to move the actions to the left hand side! 

2. They save space with a CSS hover menu rather than taking up 100 - 300 px on the x axis like they do right now. 

I often have to make very non descriptive names for the default view action buttons just so that the views don't look ridiculous. I highly recommend you make a drop-down menu like you do for the column headers. 

3. They have sub menus. Say you want to have both an Add Note & View Notes action. It would be nice to go Actions->Notes->Add || View

4. They display actions conditionally vs ALWAYS visible. 

Why not give us the ability to throw in a formula condition to before showing an action button. This way you can build ONE view that does a lot rather than having to make multiple criteria views that match before adding an action view

Here's the gist on how I build these btw. 

1. I create a formula field name actions

2. I write a function that accepts certain criteria fields from the form

3. The function builds up the menu based on matched conditions

4. I execute the function in the formula field! (Yeah, you can execute functions in formulas)

Note : Make sure that the fields you are referencing as conditions for you menu get updated otherwise the formula value won't update. 

5. Drop the view in an html view

6. Write CSS for menu. 

7. Enjoy! 

Note : The menu isn't actually using functions. It's just a list of links to open forms, viewing records in a relational way. There's no current way to execute functions from a custom menu like this, but if all you are doing is openURL tasks anyways then you can do this with a custom menu.