After Flick



After being rejected from the App store for Duncan Dance I just HAD to find a new app to create and get on the app store. Going to the movies has always been a hobby of mine, but the past few years I’ve been so wrapped up with development projects I barely go anymore. An old friend of mine (I’m talking elementary school old friend) named Michael “Mikey” Bover is my movie watching buddy. It was a common interest we always shared from the ridiculous B movies “Fear Dot Com” to the Jason Statham movie where he drives a car (try and figure out that one). This time it was The Grey with Liam Neeson on 1/28/12 5:05pm @ Kaufman Studios Astoria NY. Every movie I go to I am prompted with a question at the end of the film. Is there something after the credits?

I had to go on my iPhone to Google search for after credits The Grey and find a site that could tell me do I have to wait after the credits or not. I found sites like http://aftercredits.com/ and http://www.mediastinger.com/, which had exactly what I was looking for. It told me to wait after the credits for a hidden scene. So I did and was pleasantly surprised with what was after the credits. But most people already left the movie theater and didn’t know they were going to miss a key scene in the film. How can we prevent that in the future?

This is where After Flick all came about. I came home and started brainstorming names for the app with Mikey so I can buy the domain. I tend to find names that have the domain available so I can have @afterflick.com as an email as well as the URL. Finally after many tries Mikey came up with After Flick. I give credit where it’s due so congratulations Mikey for coming up with a name that wasn’t taken. His agreed compensation is one beer a year.

Pushing myself to the limits is always fun. I planned to have a beta version of the app done in roughly 24 hours using Titanium. For those who do not know, Titanium is a framework you can use to write code in JavaScript, which spits out iOS code (Objective C) and Android Code (Java). I quickly made a demo version after spending from 1:00pm Sunday Afternoon to 5:30am Monday morning. Yes I still went to work tired as hell but boy did it feel good.

I took a break from the code for a few days and jumped back in making everything work to my satisfaction. I didn’t want to spend time making a register page and all that login crap so I did Facebook authentication, which grabbed all of the info I needed for me. Once you log in you can vote up “After Flick Synopsis’s” and write your own.

Testing my application with others was my first priority when I was ready for the beta version. I used Test Flight to deploy my beta version on 3/10/12 to iOS devices owned by my father (Eddie) and my beautiful girlfriend (Amber). Both had some ideas in making the application easier to use from someone who never saw it before, which is always great to have when developing an app. The comments about the app were taken into consideration and pushed out three days later, which is when I uploaded it to the App Store for approval. No longer than 20 minutes after submission…dreamhost.com servers were all down and killed my app (since everything pulls from a server). They got it up and running many hours later but I’m really considering another web hosting service.

If you read my post before about Duncan Dance…I was already weary about the App Store stamp of approval since they are quite hard on their guidelines. I knew it would take a while to be “In Review” because the new iPad just came out so everyone was updating. Or they just enjoy making me wait.

Finally I got the notification that Apple was looking at my app. I quickly opened my app to make sure my server was up and running and thankfully it was all good. I checked my MYSQL database and saw the apple developer sign in 40 minutes after they said they were looking at my app. TWO MINUTES LATER…I was rejected. UGH what now Apple?

Reasons for Rejection:

2.16: Multitasking apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.

Mar 20, 2012 11:47 AM. From Apple.

2.16

We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines.

We noticed your app declares support for audio in the UIBackgroundModes key in your Info.plist, but no audible content is played when the application is in the background. While your intention may have been to provide this functionality, at the time of review, we were not able to play background audio for your app.

As indicated in the iOS Application Programming Guide:

“This key is intended for use by applications that provide audible content to the user while in the background, such as music-player or streaming-audio applications.”

Therefore, it would be appropriate to provide audible content to the user while the app is in the background or remove the “audio” setting from the UIBackgroundModes key.

For information on background modes, please refer to the section “Executing Code in the Background” in the iOS Reference Library.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to prepare any symbolicated crash logs, screenshots, or steps to reproduce the issues for when the DTS engineer follows up. For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports.

Great so I had one thing checked in my info.plist file (thanks to Titanium’s presets) that said I was using background audio services and Apple rejected me because I didn’t use it when I “claimed” I did. Frustrated after second rejection in my App history…I quickly fixed the issue and put up another version an hour later.

Exactly one week later I’m with a client discussing their online social presence / website and I get a notification on the iTC Mobile app at 9:57pm “Your app After Flick, 1.0 has changed to In Review” followed by another notification at 10:04pm “Your app After Flick 1.0 has changed to Process for App Store”. I didn’t notice the first notification because I was in the middle of a conversation but when I read “changed to Process for App Store” my body froze. MY APP PASSED! Two apple developers approved my app to go on the app store! At 10:20pm “Ready for Sale”. After checking the app store on my phone constantly after 10:20pm, it finally showed up at 12:46am. I bought my own app and I loved every second of it.

I am really proud of myself for building an app from concept to app store all within exactly two months to this date. The feeling of completion is unlike any other feeling.

[SCREENSHOTS]

[UPDATE  4/1/12]
A bug was found if you do not log into Facebook it will constantly prompt you to log into Facebook each time you click on a different movie. I’m aware of the issue and pushing out an update as soon as it’s approved by Apple.

So many lessons learned since it’s been on the app store 14 hours….

 

 

[UPDATE 12/17/12]
After many months of procrastination, recoding it natively, and waiting for Apple to Approve the new update, After Flick v2.0 is on the app store! I also released it for FREE! I am still thinking about Android but want to learn how to build it natively as Titanium didn’t “float my boat” as much as I hoped. I also spent a lot of time over the past few months learning about UI and UX to make a more fluid, easy to use interface.

 

4 Responses “After Flick” →

  1. Ben Donaldson

    March 29, 2012

    Great job man, I promise whenever I switch over to iPhone I’ll buy your app.

    Reply
    • Thanks I appreciate it! Let me know if you are still building flash games. Love to try them out.

      -Wes

      Reply
  2. If you are using Titanium, why you didnt released an Android version of your app?

    Reply

    • wesley

      April 3, 2012

      Good question. The reason I didn’t release an Android version of my app is because I haven’t had time to do so yet. Without a doubt I plan to release an Android version just want to make the bug fixes and updates to this one first then release the Android version in the next upcoming weeks.

      Thanks for the comment,

      Wes

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *