[Nova Launcher] kevin@TeslaCoil:
Do you mean a setting between None and Small or is None not working for you? If it's not working what device and density (if not stock).

Sorry, not adding people right. There's no actually private beta anywhere outside of my devices at the moment anyway. I see there's a lot of interest, which I'm thankful for and encourages me to get the next update through private testing and into public testing as soon as I can without compromising quality. I also may invite some of you for private testing in the future. But it's complicated to add people and I'd rather people didn't ask as it's clogging the thread. I will however give some insight into what private beta testing means.

Private beta testing isn't always exciting. Sometimes you get new features first, but they might cause crashes. Sometimes you don't even get new features, just new crashes for me to debug before I can introduce the feature. Introducing major changes, with potential bugs on a smaller group of people is less of a headache than introducing them to a huge group. This is also true for backwards compatibility, with releases and public betas I'm focusing on the public users, your data is valuable and Nova should never annoy you by forgetting it between updates. For private betas, my focus is still the public users, not the testers. If I can save development time, leading to a faster release or public beta, by losing some private beta user data, it's acceptable. QA wise a public beta or release I personally tested on several devices, a private beta might have only ever been tested on one of my devices before it goes out. Also new features are exciting but nothing kills excitement faster than FCs or bugs. You see this in market comments, if an app updates to add some cool new feature but there's bugs, they get 1-starred for the update introducing a feature that doesn't work. Doesn't matter if before the update the user thought of it as a 4 or 5 star app, a feature not working can be really upsetting to users. Releases and (usually) public betas are more predictable and generally lead to the best overall user experience.

When I'm adding testers, it's usually people I've communicated with (directly or indirectly) multiple times and who I communicate with well. (I'm not always easy to communicate with during testing, and I'll be needing feedback from testers, sometimes logcats, and need them not to get upset with me about bugs or because I don't reply to their emails [busy fixing bugs!] and also me not get annoyed by their emails).

I also need control over the private beta, which means trusting the testers. I need freedom to make changes (introduce a feature and then remove it, switching a new feature from Free to Prime, aggressive analytics or logging that might upset privacy conscious people or slow things down, and keeping a feature secret from my competitors who have shown no shame in blatant copying, even pixel by pixel copies of images). Public beta, or a huge private beta group, would make these things harder. Sadly I got burned by a tester once, WidgetLocker 2.0RC2 was leaked to pirate sites by someone who was supposed to be helping with translations. In those days my beta FC reporting just open a new email to me. This was kind of nice because a tester could add a description of the circumstances before pressing send. But 2.0RC2 had a common enough FC, especially when used by several hundreds of thousands of pirates even after 2.0 final was released with the fix. This happened well over a year ago but I still get ~5 emails a day from it filtered to the trash. At it's peak it was probably at least 100 FC report emails per day. I'd rather users didn't pirate, but if they're going to I'd hope they at least have a good user experience which encourages them to buy. These guys are using a bugging release that was never intended to be used by the public.

TL;DR Not adding private beta testers right now, more complicated than you'd think. It's not necessarily good to be a private beta tester as things will be broken. Being polite and communicating well along with happening to have a device or use case I'm interested in might get you invited, but please don't count on it or ask about it unless I ask first.