Lessons we learnt from EasyPin

EasyPin is the team’s first app. It took 20 days to appear online after submission. It got rejected once by us and once by the App store. ┬áSomeone might say it’s not bad, but as a professional app provider, we should never forgive ourselves for any mistakes that we make.We’ve learnt some lessons from the process they are:

  • Don’t risk adding a hacking code for a feature that is rarely used: for a page deeply embedded in the app, we added some hacking code to determine the way a page is opened according to a white list, but the white list can be easily broken as the page could contain some frame and introduce a url out of the white list. The bug is serious. It caused users to be unable to login Pinterest and of course App Store rejected it. The lesson we learnt here is, for a feature that is rarely used, we should not do too much on it unless we have 100% confidence that it doesn’t damage anything.
  • We should set proper rating for the app. Apple replied to us “Since your application allows unfiltered access to the internet, where content with mature or suggestive themes can be accessed, it should be rated 17+. Applications must be rated accordingly for the highest level of content that the user is able to access.”
  • Require “Sneak Peak” if possible. We didn’t raise any pre-buzz before the app is published. This is fine for an app that is only for experiment. But if we have a killer app, we should prepare some buzz before it’s out.

EasyPin is our first app. We admit it’s not a killer app. While we take it seriously and try our best to learn in design, development and marketing. We believe our next app will be the killer app. So stay tuned for our next App.