I don't know a thing about the API but I fully support this.

previously API can only put all addins under Add-ins Tab, now it allow users create new Tabs using new API, i believe in your case, some addins are coded in old API, some are coded in new API.
maybe i'm wrong, but i don't think you have option on where and how to organise these things unless you modify these addins, i mean coding.

HI Mark.

Great question.

1. Up until Revit 2012 we could only put applications in the addin tab other than some fancy work by GuyR who managed it fine in Revit 2011, but unsupported by Autodesk. (man us Kiwi's are bright )

2. Revit 2012 & 2013 developers now have a choice of putting them on their own panel in the addins Tab or creating their own tab. There is no old and new way of doing this.

3. It is up to the developer to decide where to put them but we are encourage to put them in the addins tab if there is only 1 or two icons. If you have a lot them making a tab makes sense.

4. There is no way to create a tab other than through code, and then there is no way of creating a tab and moving someone else's application to that tab.

5. The work around you could employ to an over crowded Addins tab is to add the most commonly used Addins to the Quick access bar or to add a shortcut key to the addin which you can now do in Revit 2013.

I hope that helps?

Cheers
Phillip

Thanks for reply Phillip.

I understand anything with more than three icons should have there own tab but other addins with just one or two, defiantly need go to Add-ins Tab, and of course keyboard shortcuts to them.
I have approached developers and asked for a switch for New Tab or to Addin Tab and it is more than possible as some have done this for me.
It seems you API guy's need to create some sort of "api standards" and incorporate these sorts of switching features or this is going to get rather messy.

HI Mark.

Yes it is easy to create a switch to either put our apps in the addins tab or create a new tab. What you can't do that I'm aware of is Developer # 1 create a tab Called "MarkB" and add their app to that tab and then have Developer # 2 add their app to that tab as well?? If you can I would love to know how.

OK I vote to make switch to new tab or add-ins tab mandatory it would solve a lot of the problem and if you guy's can solve the to "desired created Tab" thats a bonus.
In reality having them all in add-ins tab with shortcut keys works just fine and keeps the Ribbon clean.

But there is not a hell of a lot of point coding a switch to create a tab if we only have one icon is there?

Phillip I think you are misunderstanding what i am saying, I really don't want anything added to the Ribbon ("keep it clean") and put ever thing in addins is my theory, but if you guy's think your API deserves a New Tab at least give us the option to to decide, New Tab or Addins if possible.
For those who don't use shortcut keys and like going to the ribbon and selecting, then yes overcrowding will become problem and they may like to some how sort them which would mean creating a "addins 2" tab.
For me its shortcuts all the way so overcrowding is not an issue, just want to "keep the ribbon clean"

I totally agree with you Mark and it should be on if you have an extreme number of icons that you should create a new tab. None of our apps have anymore than 2.