Category Archives: Booty Caller

Reasons to be rejected/removed from the iPhone app store…

Well, some of you may have noticed that the BoSox Clock is no longer in the app store… MLB sent us a letter asking us to remove the BoSox name and the hanging sox logo from the app, and because we didn’t get the letter right away, we pulled it just to be safe and resubmitted it under the name “BoClox”.  Hopefully it will be met with equal enthusiasm… we have a Cubs themed Clock coming soon too… my personal fave so far.

This incident has caused me to reflect about all of the reasons that we have been rejected/refused/delayed for sale in the app store.  Here they are to the best of my recollection:

1.  Inappropriate sexual content – booty caller was rejected for the word booty, best we can tell.  It was later accepted as Black Book Caller. Generally, these emails simply quote one of the sections of the iPhone SDK agreement, but don’t give specific reasons…

2.  Marketing material not matching application functionality – we used some ambiguous language in the description of iDrunk Dialer.  The app reviewer minsunderstood one of our feature descriptions and rejected the app for having incomplete functionality

3.  Trademark infringement – along with MLB, Polaroid blocked our iShakeIt Camera application for using the white border.  This one was difficult because Polaroid was totally non-responsive to our inquiries about licensing the design, so we had to just let the app die.

4.  Missing controls – this is really dumb of me.  When moving back and forth between the 3.0 SDK betas and the 2.2.1 SDK, something messed up and my labels disappeared in the alarm view of BoSox Clock (or BoClox).  I was never able to get them back, so I had to delete them and re-add them as images.  This goes to show that you always need to test one last time before you submit.

5.  Application icon not matching app-store icon.  This is something that is not explicitly stated in the rules, but is pretty strictly enforced by Apple – basically, these need to match to avoid user confusion.

6.Using/referencing public figures – we learned our lesson on this one.  We had iLogan unexpectedly delayed because we has a list of people you could maul included in the description such as U2, Chuck Norris, Britney Spears, etc…  Apple was nice enough to call about this one, and so we immediately removed the offending characters and moved on.  Our app iJump to Conclusions Mat also fell victim to this – we used a screenshot of Tom S from the movie and that shut us down.  That’s another one that we just let die.

7.  Referencing the price of the app in the description – this is a new one for us, but it makes sense.  In the international store, the prices are different, so even if the app costs 99 cents in the U.S., it may cost $1.29 in Canada.  Therefore, to avoid confusion, we removed all references to the price in the description.

Hopefully, I won’t be adding to this list any time soon.

P.J. the Pony

Advertisements

Apologies and news..es…. Black Book Caller LIVES!!!

So first of all, I’m sorry that I have been absent the last week or so.  I was in California for Embedded Systems Conference and make an appearence at 7 Bamboo Karaoke.  This was totally epic, yet slightly distracted me from my bearded pony endeavors by the likes of Prince and Mr. Big.  So with that, I would like to re-embark on our blogging relationship with no hard feelings.

Now, on with the newses.  First of all, with many attempts and zero responses from the Polaroid corporation, Bearded Pony has decided to resubmit iShake it Camera as a free app… not because we want to, but because it seems like such a waste to keep it in the review queue.  Yesterday, I sent the word to Apple as so, we should be seeing it soon.

Second, and the bigger news – Booty Caller is live… sort of.

We at Bearded Pony decided to take the honorable way out and remove all references to “Booty” from the application and call it Black Book Caller.  You can buy the app here – it’s 99 cents. Please buy it.  Please.

default1img_0003

We have a couple of more apps in the pipeline, and one of those is going to be huge.  Right now, I am working on an RSS reader, so next time I will blog about how to create one of those.  In the meantime, if you’re curoius, I’ll be starting here.

Finally, we are on twitter.  So if you are in our posse, and you need to know what dive bar we’ll be watering our holes, check it.

Baby baby,
P.J. the Pony

Too HOT for the iPhone App Store

Many of you are asking what material Apple found offensive in “Booty Call”… our best guess is the “handbook” portion of the app.  We have since resubmitted with that feature removed, but for those of you loyal blog readers, here’s the content that was just too sexy for the iPhone.  Put the kids to bed, and get the cold showers ready:

Tips for the successful booty call:
1. Always know her schedule before you call
2.  The majority of the booty calls need to be at her place. A good rule of thumb is 3 to 1, average three meetings at her place for every one meeting at your place.
3.  Make sure you sleep over the first time, and then apply the 2 to 1 sleepover rule when developing a booty call relationship. You should average one sleepover for every two times you don't.
4.  If it's the first call, talk for about 5 minutes before testing the waters. If it's not the first call, keep the talk under 3 minutes... she knows what you're after.
5.  Start with "Can I come over?"
6.  Is she asks you why you want to come over, try "I just want to see you for a little while."
Common excuses you might encounter:
* She is tired -- You'll have to play this one by ear and listen to her tone of voice. If she doesn't sound tired, follow up with the, "I just want to see you for a little bit" line.
* She is going out that night -- tell her you'll come by after she gets back
* She has to do some work  -- say you'll come by after she's finished

Stay cool, kids.

P.J. the Pony

0 for 2 – Booty Caller iPhone application rejected for objectionable content

So, it looks like Apple’s newly found “liberal” approval process does not yet apply to apps with “Booty” in the title.

We got word today that Booty Caller was rejected by Apple today… here’s the email:

We’ve reviewed Booty Caller and determined that we cannot post this version of your iPhone application to the App Store because it contains inappropriate sexual content and is in violation of Section 3.3.12 from the iPhone SDK Agreement which states:

“Applications must not contain any obscene, pornographic, offensive or defamatory content or materials of any kind (text, graphics, images, photographs, etc.), or other content or materials that in Apple’s reasonable judgement may be found objectionable by iPhone or iPod touch users.”

Bummer.  I wrote them back and asked how close we were to see if there are small changes/omissions that we can make to get it in.  They haven’t been terribly responsive to my questions around the iDrunk Dialer rejection, so I’m not optimistic.


The beginning of the beginning… Booty Caller is born

So, we here at Bearded Pony software have submitted our first iPhone application to the store.  It’s called “Booty Caller” and we are pretty pumped about it.  Here are a couple of screen shots to get your juices flowin’

I am an engineer by trade, and overall, I have been extremely pleased with the development experience and the APIs that have been developed by Apple.  I can appreciate that not every component has an API – it’s better to give developers a robust API for 50% of the peripherals than a half-baked API for all of the peripherals.  Based on our (albeit limited) experience, there are a couple of tips that I can already give to the budding iPhone application developer.

1.  Tab bar icons – these are a little tricky if you don’t know what you’re doing.  Make sure that they are grayscale png files with transparent backgrounds.  The recommended size is 30 x 30.  If you don’t make them transparent, they won’t show up.

2.  Certificates and provisions – this has been by far the weirdest part of the development process.  It seems like a lot of mindless clicking that could easily be automated.  The best advice that I can give here is that if you ever come across a code sign error, just cut your losses and start over by deleting everything from your keychain and generating all new keys.  It’s not worth it to troubleshoot, and the forums and apple support can’t really help.  It’s shady, but honestly, I lost a week messing around with them and I could have been up and going in 1/2 hour.

3.  I stumbled upon some weird errors when returning control to the application from some of the supplied view controllers from apple (for example, the PeoplePickerNavigationController or the ImagePickerViewController).  Sometimes, the properties of my IBObjects (like font size, hidden, etc) would go back to default settings for no discernable reason.  So here, I recommend that you take nothing for granted and set all of your object properties again when returning from the controller… just to be safe.

4.  Videos are the best way for me to learn.  This is simply becasue it forces me to actually follow along and type the code instead of copying and pasting.  Not the most efficient ,but the best for learning.  Here are a couple of the best resources I found:

http://iphonedevcentral.org/ – these kids put together some really useful infomation for beginners and intermediates alike

http://icodeblog.com/ – totally awesome step by step tutorials – these were great for learning about Tables and Contacts especially

http://daringfireball.net/misc/2007/07/iphone-osx-fonts – a useful list of fonts on the iPhone

More to come,

P.J. the Pony