• Mark Biegel

    How to upload your iOS app to TestFlight for distribution/beta

    By Mark Biegel,

    This is a quick guide to upload your app for distribution through Testflight.
 It assumes you have the appropriate access to both and

    You will need:

  • Mark Biegel

    Making iOS & Android apps with Rails & Turbolinks

    By Mark Biegel,

    So you want to build an app? One of the first decisions that needs to be made is one of time and resources. For a business, it is crucial to know your market in order to successfully launch your product. But what about the App market? Which platform you do you choose to launch to first? Apple? Android? Web?

    At this point you might have already considered a HTML5 web app so you can be cross platform and launch to everyone. Or perhaps you decided against it, due to poor performance and not having a “native app” feel.

  • Ildikó Tuck

    Five UX tips for better mobile apps

    By Ildikó Tuck,

    We have reached the point where if your business doesn’t exist on mobile you are suffering serious disadvantages regardless of what you are selling or providing. Deciding between what to build is a topic that needs its own blog post. Discussing the native app, hybrid app vs mobile website/responsive website topic is a separate one that I wouldn’t like to get into today. For the purposes of this post I will assume that you have decided on the right solution for you and that happens to be a native app. What can you do to ensure its success?

    Context is crucial to the success of any app. With the web it’s easy - people will be using it while sitting at a desk or at least sitting with a laptop somewhere. With mobile, it can be any number of places and situations. If you’re building an app for runners, think of what features they can and should access while running. For example, for a runner it’s very useful to know their heart rate, their speed, track their movements on a map, see how many calories they’ve burned and have the ability to share their progress with their peer group. All of this is great to have in a mobile app, but should you have it all present at once? Or does it make sense to have a big “Start/Stop” button that takes up the whole screen? If you go with the start/stop button, how large should it be? What’s the ideal size to prevent accidental taps while in motion, but at the same time prevent the runner from having to stop to activate it? Or, what about a GPS app for mountain climbers? They probably don't have available hands to fiddle with their device while trying to keep safe. What features are still useful, and how can you ensure that your app is actually usable in the real world?