I hate to disagree with you but I have some counterpoints.
1. You think your interface is cleaner than BlueSocket? Does it matter considering I think i give the user better error feedback when a condition goes wrong and also if AutoClose is on no one sees our interfaces?
Yes I do think my interface looks cleaner, but it's a subjective opinion, if you don't like you're welcome to disagree. I happen to like the way mine looks. As for error information, BlueLogin provides lots of information on various possible outcomes and tries to alert the user as to what could be wrong. Since you bring that up, I would ask if you have used BlueLogin yourself, or are you making things up?
2. And which option do you think yours has that mine doesn't? The fact you make the user enter Google as a parameter is a waste you don't need it. Verifying SSL?
Actually google is pre-entered, the user only needs to give a username and password and they're set. All other options are set to sane defaults. The user is able to enter a website other than google because they may be connecting to an intranet or to an ISP that does not have access to google.com. This is arguably a rare case, but considering changing the field is optional, this provides added functionality with no downside to the user.
Verifying SSL is an important feature because it is trivial for someone to setup a dummy network in order to mount a man in the middle attack and steal passwords. Verfying that you're sending your password to a valid SSL server helps to provide the same guarantees you get when you use SSL to order things on the internet or login to a website. Again this is on by default, and the user doesn't have to set it up to use it. I left it as an option because I was not sure if all BlueSocket servers provide authentication over SSL, otherwise it should always be left on.
SSL provides both encryption and identity verification, if you think these are somehow unimportant, I'd like to understand why you think so.
3. You have been around longer? I submitted mine to the AppStore 3 weeks ago it just took Apple 3 weeks to approve so its not like I quick whipped it up...yours has been out exactly 9 days before mine and that could have been the approval process lag time.
We all have sat around in the queue for weeks at a time, apparently I submitted a little sooner. I am not trying to say that this in and of itself makes BlueLogin better, but it does mean that it has spent more time being used. This means I have already received user feedback and have already started improving BlueLogin (updated version already in the review queue). Your app is relatively untested, but that doesn't mean it's worthless, nor was I trying to imply that.
4. You have 3 reviews. I have 1 and mine has been out all of 15 hours. I don't think that is a fair comparison?
Again, more users, thus more user feedback, and already working on improvements.
So before you lambast BlueSocket Authenticator I would hope you would have done your research. I did not go around telling everyone not to use BlueLogin? They can choose which one they think is better...isn't that Free Market Capitalism?
There was nothing angry nor demeaning about what I said. I gave a subjective opinion and added some information to help the user decide what they might want. Actually I said precious little, and offered them a link to look for themselves. I did not tell anyone to stay away from your app, they're welcome to use what they want. However, pretending like I am attacking you in someway is a little silly. If you truly wanted a free market you wouldn't be so aggressive towards someone who is only offering an alternative to people.
Either way, good luck.