Apps

App Store

Something we used to talk about in university was the impact an operating system can have on people. A system designer imagines the future and creates capabilities that its users can leverage. It is a form of influence on users to adopt the imagined future. Users, however, behave in unpredictable ways. A system starts to take a life of its own when users leverage these capabilities in creative and innovative ways the author didn't anticipate. This leads to a relationship between the two parties where they influence the future together through observation, experimentation and imagination.

Mobile operating systems are the most impactful operating system of our day. Billions of people are in a serious, intimate relationship with their mobile devices. This relationship, however, is not a traditional 2-way pairing. Modern operating systems have APIs that application developers can take advantage to enter into this conversation between users and system authors.

App stores are a crucial piece of this relationship. They directly impact the type of relationships we have and who we meet in this ecosystem. That shapes our experience and our future.

Apple should be careful steering its App Store.

App Store policies have a specific function: policies keep the ecosystem at a healthy state. Healthy ecosystems grow and flourish. Apple's main viewpoint in keeping its store healthy is to create a safe environment. This ecosystem is diverse, many of whom are non-tech-sperts (like my mum), who needs help with technology. This is a good strategic differentiation for Apple's brand and offering.

Safety has a lot of layers. To name a few: protecting users from scams, preventing issues on devices, enforcing age appropriate content and privacy, are all parts of feeling safe. These help users.

Developers also need safety. That is done by having access to robust tools, cover from external pressures (like litigation) and an environment where they can compete fairly to gain the favour of users.

App Store does implement many policies around these issues. They scan applications, weed out bad actors, have features like "privacy labels" to ensure transparency. For developers, they provide tools, APIs that make it easier to build wonderful experiences and at times, protection from litigation (from pesky patent trolls).

The issue is that App Store policies aren't all targeted at creating a "healthy ecosystem". They are also targeted at the ecosystem yielding high revenue. Now that most people who needs an iPhone has an iPhone, growth has to come from services and future hardware products. App Store revenue is important to this formula. This is similar to issues faced by Netflix: successful companies running out of room to grow.

There are few spots being targeted for revenue on the App Store: payments, ads and competing services.

Ads are not on brand for Apple. It is a premium product, nobody wants to see cheap casino ads. The issue here is that ads are in direct competition with privacy. Good ads are context sensitive and relevant to the user. Recent ads debacles show that they need to dive deeper to make a great ads product (the kind Kevin Systrom will be proud of).

The payments situation is a mess. There was clear thinking around app sales tax (30%) and in-app purchases for a while. However, users and developers are behaving in unpredictable ways. Technology is moving quickly with new payment types and ways to deliver experiences. The system author has given rise to these innovations but now has to grapple with the reality that they don't generate revenue.

Few things come to mind:

  • Bitcoin, Blockchains and NFTs have ushered in new ways to own and purchase goods. App Store policies are hurting NFT trading altogether.
  • Games are moving towards subscriptions and "stream on any device" models. App Store policies simply don't allow for such innovations to play in the ecosystem.
  • Modern day social media was born out of iPhones. Their existence has transformed many areas like marketing, shopping and entertainment. App Store is yet again trying to apply old rules onto these new spaces.

Read more: Apple flexes its control over App Store

These actions show App Store is unprepared for the innovation that is flourishing in the ecosystem.

Beyond payments, Apple is competing with other services in the App Store like music streaming. This is causing developers to realise the relationship is not built on mutual trust and equality. There is a clear dominant party here.

So, there are some problems.

Apple's focus has been to increase revenue from its service offerings. That has required them to test the boundaries of the relationship they have with developers and users. All the while, the platform is moving forward in unpredictable ways. Innovation is taking place under their noses.

I think it is time for Apple to observe and adjust its policies and systems so that innovation continues on their platform. I dislike seeing developers pull features from their apps on iOS. It is feeling like owning an iPhone has become a disadvantage.

There is nothing wrong with getting return on the investments made on these amazing devices and software platforms. It has to be done in a way that doesn't strain the relationship we have with them. The only real way to make long term revenue from services is to work on keeping the ecosystem healthy. It needs to stay safe and have room to grow.

Why techies make crap early adopters

Recently, I’ve been working on apps and business ideas like AlwaysHungry, 60Hz and Secret Hotels (for lastminute.com.au). Finding early adopters to test these products are not easy. Things are even more complicated because my friends and colleagues tend to be very tech savvy.

It seems like people associate early adopters with being able to use a phone really well, or know their way around Safari with shortcuts on a Mac. What I observed in my time observing people using things I build is that they use products in anger.

What do I mean “using in anger”?

These users deal with the app in an aggressive manner. They press anything and everything. There is no real purpose behind the usage. They experience the product in a very detached manner.

There’s nothing wrong with all of this. In fact, it is a great form of stress testing. What sucks about it though is the lousy feedback you get. Feedback that sets you down the wrong path because the content never spoke to them in the first place.

Comments like “this button looks out of place”, “I like how Tweetbot does it” is irrelevant if they had used the app with a real purpose. These forms of feedback generally point you towards whether you’ve built the product right, not so much if you built the right product.

I think this contributes to even the biggest companies in the world building things that are irrelevant. Designers and developers build things to be used in anger. They go for rounded corners and bug-free apps rather than apps that flow well and really work hard to present content well (rounded corners rarely help the cause).

Reddit is the most relevant example I can think of. That thing looks like a shit website, reminds you of a dirty alleyway in the city somewhere. But it works. It’s got such awesome, random, awesome content I keep going back to it!

Back to early adopters.

If you want these special beings, find places they hang out in like forums etc. Look for people who are already solving the problem manually and bitching about it. The most important quality you are after in a person is that they are “someone who endures bugs, lack of rounded corners and much much more for the right content or solution”.

Good Luck!

Apps that grow with you

It's difficult to make a good app. But it's even more difficult to make an app that grows and matures with the user: something that starts off basic and overtime, as more knowledge is shared between you and the app, more in-depth features are revealed to appeal to a more mature, advanced version of you.

Thought I had while discovering something completely new after a week of using the Jawbone UP fitness band.

iphone-20130801221737-0.jpg

Important Considerations Before Naming Your App

If you’re a small time developer, you generally tend to skip steps when it comes to following a proper process on naming your apps / products. Here’s a list of things you shouldn’t be skipping...

Say you decide to make an app to educate people about how bad donuts are. Let’s call this app “Evil Donuts”. Excellent name!

Step 1: Google it.

This is so easy to forget sometimes. Always Google and see what comes up. Then switch over to the “Image” search tab and see what comes up there. If you only manage to get one to three bikini women, it is a good sign! These are the things that would compete for SEO and the things people associate your name with.

Screen Shot 2013-07-07 at 10.32.46 AM.png

Damn it, Facebook Group is taken. Might have to name it “Evil Donuts App”.

Step 2: Domain Search

Domains are important. We need to look for www.evildonuts.com and www.evildonutsapp.com. These are good domains for our app, unless your aim is to introduce a submain on your own site like: www.m2d2apps.com/evildonuts.

Screen Shot 2013-07-07 at 10.34.41 AM.png

Bummer, someone parked it.

Screen Shot 2013-07-07 at 10.35.13 AM.png

I recommend you use https://iwantmyname.com/ to look for names. It checks pretty much every domain possible.

Step 3: iTunes / Play Store

Ok let’s say this is going to be an iPhone app. We have to fire up iTunes and see if an app with that name exist. If it doesn’t great. If it does, you have to decide whether to stick with it. If you do, you can simply extend your name to: “Evil Donuts - Junk Food Eating Tips”. When the user installs the app, you can still name it “Evil Donuts” without Apple freaking out.

Screen Shot 2013-07-07 at 10.36.35 AM.png

Score! No Apps! Just like our 60Hz App!

Step 4: Easy to type?

We never thought about this when we launched “Notes + U”. Terrible name. Worst of all, it was hard to type on the iPhone. iOS keyboard hides the “+” button under 2 levels in the keyboard -- BAD idea. Make sure it is hard to misspell and easy to type out.

Step 5: Trademarks

Disclaimer: This is not in any way legal advice. Get a real lawyer for that. I am not qualified. This is merely personal experience.

CHECK TRADEMARKS! If your app only ever sells 10 copies this is less of an issue. However, if it makes its way up the ranks and you start gaining some love from Google, then you are in for it! “Evil Donuts Inc” is not going to be nice and empathise with your situation. Trademark law, I believe, specifies that once you have a trademark, you have to actively defend it or risk losing it altogether. So chances of you getting a Cease & Desist letter is quite high. Unless you have a strong legal team you will be forced to pull your app from the store when this happens.

Generally you will be forced to take down everything you have related to your beautiful app once you get a letter. Game over.

Interesting things I found out:

  • If you made friends with a law grad, good for you. Love them, buy them dinner, and keep in contact.
  • There's less likelihood on infringing trademarks if the name is descriptive. For instance, if we had named our app “Donut Nutrition Tutorials”, it is quite hard to get a C&D due to its descriptive tone. However, if we called it “DonutNutritionTutes”, then it is still under threat!
  • Generally trademark disputes resolve in the favor of the trademark owner. So you are very likely to lose even if you contest it.

Check the following countries at least:

Screen Shot 2013-07-07 at 10.38.26 AM.png

Cool! Abandoned in 2005!!


Once you are happy, go ahead and create an app in iTunes to stop anyone from taking that name.

Happy building apps. Evil Donuts app never did get made.

 

We changed looks. Now we change names. Your favourite TV tracker is now running at 60Hz.

tvQ is 60Hz.

We had a great launch for our latest TV tracking app about a week ago. It's a new app rewritten with all your feedback from 1.0, with a fresh take on TV and movie tracking and of course, a fresh new icon with a sleek new user interface. Now it's time for a new name too!

What are we in essence?

We are all about your TV experience. At the end of a hard day's work (or play...) you sit down in front of your TV for a pause, to escape to another world. Our app is your assistant and your guide on this journey to other wonderful worlds of imagination. The television is the center of this experience and believe it or not, it flips the frames 60 times every second to immerse you deep in this experience. Our app, helps you stay in sync with your TV experiences at all times, which means we're running at 60 frames a second too. So we called the app, simply, 60Hz.

60Hz

We, here at M2D2, want to keep pushing 60Hz in this direction of helping you to get the most out of your television time. We'll be adding new features to make your TV experience more entertaining.

When 2.1 launches, we'll officially change names. When it does, tell your friends. Your recommendation is important to us. We depend on it heavily to keep the app moving forward. We've been prompt to answer all your feedback. We've gotten over 30 emails on the first few days alone! We have a good idea of where we can improve and what we can do in future releases. So keep the feedback flowing...

And spread the word about 60Hz!

Designing 60Hz 2.0

I love watching TV shows. I spend about an hour a day on it at least. It’s not just TV, I love movies too. I love the stories in them. It is another world of imagination where there are no limits. I gravitate towards shows which have a long running story, like Game of Thrones. I appreciate the sense of continuity they have. These shows offer a way for me to escape my busy work day when I get home.

In the December break of 2011, Suneth and I were geeking it out trying to solve a very small problem we had with TV: I find it hard to keep up with the story. Often, the episodes aren’t in order. Even if they are, you tend to forget it a little here and there. Busy life gets in the way of tracking these things. So we decided to make a little iPhone app, called tvQ, to keep track of where you’ve watched something to.

So tvQ 1.0 came out. We drew inspiration from apps like Series Guide for Android, which I had been using on my Nexus One. We got some traction after Justin from Trakt.TV approached us for an integration. 50% of our users are from trakt, the last time we estimated the numbers, which is a huge deal.

tvQ v1 is slow. It suffers from slowness brought on by Core Data Framework. We probably didn’t know the right way to go about it, to be honest. It is designed with stock standard iOS controls, which look dated now. We wanted to give it some love and write it in the architecture some of the bigger enterprise grade apps are written in. We wanted it to be fast and focus on the user experience a lot more this time. Other apps for trakt were copying our front page so we thought... let’s make something better! (Haha)

Coming from Momento Jar app, we had sharpened our iOS + Design skills. We started sketching out some of the early designs as you can see here (and some early photoshop mocks):

These screens represent some of the thinking gone behind the new design. Initially we wanted to take the 1.0 experience across where we focused heavily on just a single list of shows with their next episode. A lot of the times, this design didn’t always perform well. We realised the main page was more about episodes and less about each series. So we spent time crafting the front page to be episode centric.

Now, episodes from each show are put into 3 buckets.

  • We always show you what’s on today. They don’t have to be next in line. It is to say... hey these shows are on today, which might spark your interest to catch up or just see where it’s at now.

  • Next is upcoming, which is what I look forward to in the coming week. I get some of these stuff online so I keep an eye on these. Sometimes I like to read in advance and see what’s in store for the following week (I skip ads on TV so I don’t see the previews). I can limit this section by saying don’t show me if the next episode is 6 weeks away or more. When Suits is returning in a few weeks time, it will start appearing on the list again... which is exciting!

  • Same goes to past episodes. The thresholds you set for yourself allows shows you neglect to fall off the ledge and stay out of your way. Make sure to set these up in your settings when you get the app.

We added a proper library for you to collect shows. Made it so that you can ignore missed episodes for shows like CSI where you don’t care about watching every single episode. We made comments part of the synopsis page to see immediate reactions from other community users (trakt only).

iOS Simulator Screen shot 22.04.2013 8.06.47 PM.png
iOS Simulator Screen shot 22.04.2013 8.08.02 PM.png

One big change this time around is artwork. We put fanart and posters in the center of everything. This doesn’t mean we compromised on design at all. They elegantly fit in and add color to our app. You will realise the app is white for most part, with neon styled icons. The rest of the colors are really added in by the great artwork, giving color to every page. Our experience with Momento Jar really helped out here. There’s a bit more technical knowledge involved in caching, cropping and animating images to get the most out of them. If you get the iPad version, you will see that the obsession with great artwork continues. We hope you love it!

iOS Simulator Screen shot 22.04.2013 8.50.57 PM.png
iOS Simulator Screen shot 22.04.2013 8.29.36 PM.png
iOS Simulator Screen shot 22.04.2013 9.00.26 PM.png

We did a lot of work in the backend too. It is a brand new codebase. We threw out everything we had before and made everything super fast. We used the Command & Engines architecture (future blogpost...?) to organize everything properly.

In the end, we’re very pleased with the result. I think this is a world class app, for both iPhone and iPad. It is made with love by Suneth and I, who uses the app on a daily basis. We hope our effort will convert to a large number of downloads. Tell everyone about it! It’s available 10th of May. Our app experience puts us firmly in front of the TV tracking apps out there. We intend to be creative with our features in the future releases. If you have awesome ideas of your own, head on down to our 60Hz page and start a discussion about it. We love hearing everyone's take on the app and the community support.

Thank you for reading. Here’s the end result (we felt serious about the app that we made a video about it!!!). Tell your friends... iPhone app is FREE on the 10th!!! :)

Making 60Hz App Demo Video

Product demo video can go a long way in promoting your product. However, getting a video done is quite difficult. Usually an app developer isn’t equipped with video skills. External sources can quote for a video anywhere from $5k to $20k, which is quite steep!

With the launch of 60Hz 2.0, we wanted a video to tell our story. We have excellent UI and it is dead simple to use. So here’s how I created a video for 60Hz with the help of my trustees Suneth (other half of M2D2) and Dilani. If you want something similar done, approach me or follow these steps!

First, the end result:

 

1. Thinking...

This is my first ever video creation. I do watch a significant number of TV shows and movies so I understand a little bit about what makes a good video: It is a good storyline, coherently captured in a series of sequences, and stitched together with an uplifting track.

A lot of product demos come with a narration to help the story aspect. However, it was obvious that there wasn’t enough time for that; I had to get this done in 2 weekends to kick off marketing.

2. Writing the Script

Every good movies and shorts start with a script. Ever heard of “failing to plan is planning to fail”? Same goes with a movie script. This is where planning starts.

I came up with a tagline / theme for this video: ​”tvQ: keeping up with the story”. This proved to be an important part of making the movie. Everytime I had to make a decision, I asked myself, does it help me get to my theme?

IMG_8284.JPG

This theme is exactly what 60Hz (formerly tvQ) does; it helps me keep up with all the great stories on the telly. Being in the country where back to back episodes are almost never from the same season, it makes me less frustrated too!

I wrote down how I would tell someone about 60Hz; a little pitch. I presented the problem I was having keeping up with times, downloads, repeats and how 60Hz just lets me consume everything in order. I took the script to Google Docs and had a shared editing session with Suneth (other half of M2D2) and Dilani (trustee M2D2 sidekick advisor, aka Suneth’s wife).

3. Storyboarding

All good videos need to be storyboarded. We did the same with 60Hz video. This is a very important step. I don't quite have a pretty storyboard so here’s a substitute from Momento Jar (a video that never got made):

​MJ Storyboard

​MJ Storyboard

This was important because between the storyboards and the script, I could write down a list of sequences and estimate length of the sequences I required to complete the video. I wrote down a long list of shots, including zoom levels, to shoot. The list also had things like still shots I made in Photoshop afterwards.

It looked something like this:

Required Scenes

  • ​Pressing on icon ( < 1s )
  • Start screen up, scrolling down ( 2s )​
  • Pressing community episode on the main list, reading the synopsis
  • (Zoomed In) new show being added (probably do a few and make it a cool sequence)​
  • ...​

4. Quick Hack

Then I did something silly and unexpected: I shot a quick video!! I was impatient and just wanted to learn iMovie (never used it before). So I spent the next 4 hours on making a self shot quick video around my script. I cannot post it here due to copyright restrictions on the music I used (Change of Seasons by Sweet Thing). Message me privately for a link.

Something great came out of this exercise: Lots of feedback!!! I figured out everything good and bad witch what I did and carried on to shooting it all properly.

5. Lights, Camera, Action!

Equipped with a list of sequences, we got shooting. Interesting lessons learnt:

  • Mid morning shoots are the best for the right kind of light. iPhones screen causes havoc on contrast balance on them point and shoots. I wish I owned a DSLR.

  • Tripod is a must.

  • Little details matter, like arrangement of icons on the iPhone home screen.

  • Let the video start and run off for 5 to 10s at least. Helps during editing.


6. Editing

With my newly acquired iMovie skills, editing the video wasn’t a problem. Just have to play around with transitions, cuts, speeds, sounds etc.

Music is the one big problem. Most music is out of bounds due to copyright restrictions. YouTube automatically detects and flags your video if you misuse stuff, which is why YouTube is full of covers. EMI Music was asking what our payment was going to be so we looked to royalty free music. Here’s a great site: www.premiumbeat.com - $40 for a full track.

Conclusion

In the end, the video looks great. It gets the point across and shows off our apps. I think it’ll make a big impact on our way to the 60Hz launch on 10th of May. I hope people will appreciate the effort spent. It’s just as fun to make a video as it is to make the app itself. If you need help with your video, send me a message ;).

Remember to get your free copy of the iPhone app for FREE on launch day. 

https://www.facebook.com/tvQapp

Wisdom on Pricing Software

Recently ​I came across this excellent blog post, "Million Dollar Art", by Nate Otto on the Signal vs Noise blog. I started thinking, how relevant is it for software? Can you simply put a million, or even 30 grand price tag on software?

​We first discussed it at work and there was the rational opinion that IT products help save time and effort. If a single person's job can entirely by done by a piece of software, then it should worth that person's salary. This makes valuing software quite easy!

Why think when you can Google. I came across this wonderful article at Smashing Magazine: You're pricing it wrong: software pricing demystified. It talks about the rational price vs. the perceived value of a product. Seems like branding, good marketing, superior design, support, average price for competing products and a number of other factors can increase or decrease the perceived value of a software. Read the whole article and some of the related links to get a better idea. Highly recommended!

​When it comes to apps, the perceived value always seems to be much smaller than the app is really worth. 99 cents is very popular on the App Store. However, I think it will be wise not to go with the flow and really think about your audience and what they'll be willing to pay. Better yet, try to bend your ideas to fit to an audience which has more money to spend (Business Store for example...). Most importantly, be flexible. Start with a slightly higher price and be wiling to experiment with the price. You can never know for sure. Don't give away anything for free.

​There's one caveat: iTunes rankings! Giving an app away for free might mean that you get more downloads on launch day, provided you run a great marketing campaign. Then, things become real tricky moving forward.

We're about to do some testing with pricing with the launch of tvQ 2.0. Will write my findings post launch.