mtjc keys facebooked stamp

Episode 32 – WTF: Why the FaceBook?

This week we discuss the challenges of marketing your app from a developer perspective. We touch on Facebook’s F8. We debate Instagram’s Layout for iOS similarities and app name confusion with Mike Swanson’s Layout. We talk about the cross-platform crisis that developing for the Apple Watch introduces to users of the third party iOS developer tools.
Picks: Becoming Steve Jobs, Launcher and Mr Jump

* Sorry I forgot to put my echo shield behind my microphone – Tim

Episode 32 Notes:

App Store Review Guidelines History (diff)
Joe Cieplinski on marketing your app
Release Notes – the Business of iOS and Mac Development
Fantastical 2 for iPhone – Calendar and Reminders
Made to Stick: Why Some Ideas Survive and Others Die
Contagious: Why Things Catch On
Mobile Marketing: 99 Ways to Get Your App Noticed – Parisa Foster
Mark Pavlidis Co-founder of Flixel – YouTube
Apple Developer Relations
Layout by Mike Swanson
F8 2015
Apple Watch and the Cross-Platform Crisis
Creativity, Inc.
More Than Just Code – Episode 10 – I am the one who knocks.
Start With Why – Simon Sineck TED Talk
Magpie Video (@magpievideo on twitter)
Relive Events on iOS

Episode 32 Picks:

Becoming Steve jobs
Launcher with Notification Widget 
Mr Jump

2 thoughts on “Episode 32 – WTF: Why the FaceBook?

  1. Darren Baptiste

    It always seems that developers rush their marketing efforts to coincide with the end of the development cycle.

    An alternative could be to write the code, and consider it finished when it’s finished.

    Once that’s done, take a deep breath, and start the marketing process. The code won’t go stale while you work out a marketing plan. The code will work just as well if you set it For Sale the same day the AppStore reviewers bless it, or a month later, after your marketing effort is in full swing.

  2. Robert Chen

    A bit of a late reply, but I’m listening to past episodes.

    Regarding the segment on the “Apple Watch and the Cross-Platform Crisis,” there’s actually a spectrum of cross-platform frameworks out there that vary depending on how far they abstract the API.

    On one end, there’s PhoneGap which tosses the native API out the window. I wish them luck on getting Apple Watch integration to work. On the other hand there’s Xamarin classic which has a 1-to-1 mapping to the native API, and can even do extensions and Apple Watch.

    I just wrote a blog post on the subject of hybrid vs cross-platform vs native, explaining why native is still the way to go:


Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.