<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aaron Stephenson on Medium]]></title>
        <description><![CDATA[Stories by Aaron Stephenson on Medium]]></description>
        <link>https://medium.com/@azzoor?source=rss-802f18ee4183------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7g8h3lNbNX-0plwl5UH3Fg.jpeg</url>
            <title>Stories by Aaron Stephenson on Medium</title>
            <link>https://medium.com/@azzoor?source=rss-802f18ee4183------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:08:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azzoor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tips for launching your app]]></title>
            <link>https://medium.com/@azzoor/tips-for-launching-your-app-4fa16da1a530?source=rss-802f18ee4183------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fa16da1a530</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Aaron Stephenson]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 20:36:36 GMT</pubDate>
            <atom:updated>2018-03-06T21:49:44.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q2HQQd2L31adIO9q." /><figcaption>Photo by <a href="https://unsplash.com/@spacex?utm_source=medium&amp;utm_medium=referral">SpaceX</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve been involved in alot of app launches over the years and I see the same things over and over again. A lot of entrepreneurs believe that once they launch their app that’s it, set and forget. They think of their app launch as a single event that checks a box and they don’t need to worry about it anymore.</p><p>Yet, the event is more of a first step in the process of launching an app. Launching an app and making it successfully is more then just uploading and expecting users to come running.</p><p>After your app launch it’s a continuous process of tweak, test, analyse and repeat. You’re performing micro experiments on your app to see if users are more engaged, less engaged or neutral. Alternately you’re only tweaking your app in small ways, not completely redesigning it. The goal is to make an app your users are more engaged with and are happy to use.</p><p>Today I’m going to be running through some strategies for planning beyond your app launch and some marketing pitfalls I’ve found from past and present clients. These pitfalls are often areas overlooked by entrepreneurs.</p><h3><strong>Look beyond the initial launch</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vsitVBD7wm4AT70_." /><figcaption>“A long empty asphalt road through dry plains with snowy mountains on the horizon” by <a href="https://unsplash.com/@bbergher?utm_source=medium&amp;utm_medium=referral">Bruno Bergher</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Avoid being too focused on gaining users</strong></p><p>After launching your app, entrepreneurs often make user acquisition their key metric and don’t focus on the important stuff like making changes to their app and keeping their users engaged. You’re not going to get your app right first go and their isn’t anything wrong with that, even though you’re building your app for a problem, the users will decide if your design is intuitive and solving the actual problem.</p><p>Instead of investing a heap of money into user acquisition on launch of your app, you should think of how you can get cost effective user feedback. Most importantly feedback on the areas you think can be improved or that users are complaining about. Once you get your improvements list, quickly fix those issues, then look to spend more on acquisition (only once these problems are solved and you’ve boosted retention rates).</p><p>The short term post launch goal should be aiming to boost 30 day retention rates, and getting users to leave positive reviews and ratings on the App Store. After which you can then start to think about both paid and unpaid strategies to increase your user base.</p><p><strong>Post Launch App development</strong></p><p>A lot of entrepreneurs spend so much time in development and trying to get their app to market they forget about the all important post launch. Launching an app can be a complex and time consuming process. One solution to this is to use a “continuous delivery” approach.</p><p>The “continuous delivery” approach is used at such companies like LinkedIn (<a href="https://www.slideshare.net/InfoQ/the-evolution-of-continuous-delivery-at-scale-linkedin">Jason Toy</a>). The approach involves measuring and assessing the product in real time (analytics), along with quick iteration of app updates (tweak and update).</p><p>Some tips for adopting the “continuous delivery” approach:<br>1. Map out your 6 month post launch plan, how often will you update? Try to get into a schedule of small updates every couple weeks.<br>2. Create product roadmap for features that weren’t necessary for the first version of the app, such as new features, UX enhancements, API optimisations and bug fixes.<br>3. List out your short term and long term goals for your app, what retention rate would you like to see each month? 10%, 30%, 50% etc. I’d start with 30% for the first 30 days as a base and try to improve. Your retention rates will vary depending on your app and the duration you’re tracking.<br>4. Draw up a budget for the technical delivery and marketing campaigns for your launch.</p><h3>Marketing Pitfalls</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lgucedJ5Cd7tX7Xu." /><figcaption>Photo by <a href="https://unsplash.com/@jamessutton_photography?utm_source=medium&amp;utm_medium=referral">James Sutton</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Not getting marketing involved soon enough</strong></p><p>Planning the marketing activities for apps is another area of neglect during app development. Often entrepreneurs only get marketing teams involved very late in app development or don’t think about it until a week or 2 before launch.</p><p>This puts the app at risk of failure as the marketing team are often the ones that would plan the go to market strategy and need to understand every detail of the app.</p><p>Some items your marketing team should cover off include,</p><ol><li>Identifying what makes your app unique.</li><li>Optimise for the App Store, a crucial part of your app including App Name, Keywords, Screenshots, App Icon, Description and Video previews.</li><li>Creating a press kit.</li><li>Promotional deadlines, a timeline for all activities to be carried out.</li><li>Blog about the development progress on your website or medium :)</li><li>Contribute to feature names. Developers naming features is often problematic, marketing can help by making feature names “easier on the ears” and “on brand” for your business.</li></ol><p><strong>Social media comments and feedback</strong></p><p>Neglecting feedback is one of the most irresponsible things an entrepreneur can do. While marketing, your goal should be to improve communication between you and the user. This includes but not limited to searching Twitter, Facebook, Instagram and other social media platforms for your app name, responding to users comments.</p><p>Interacting with users on social media is a very powerful tool, not only will it help your users, it will also show the users friends or followers that they use your app and that you are communicating. Over my years I’m noticed a trend in the effort users will put into complaining about a product compared to giving praise. Keeping your users happy should be your ultimate goal.</p><p>Don’t forget App Store reviews as well, Apple now allows developers to directly reply to a review. This is huge, as it allows you to interact with a review and sort out any issues a user might have. Other potential customers browsing the App Store can see this interaction so its handy if multiple users have the same issues or concerns.</p><p><strong>Incentivise users to spread the word</strong></p><p>You should provide your users with incentives that’ll encourage them to share your app and in exchange for sharing they’ll get something for it.</p><blockquote><a href="https://www.invespcro.com/blog/word-of-mouth-marketing/">People are 90% more likely to trust and buy from a brand recommended by a friend then some marketing material.</a></blockquote><p>With that stat you would be crazy not to ask users to share your app with their friends. Just keep in mind they won’t do it for free, you’ll need to give them something in exchange for sharing. In the past I’ve used features only available to users who have shared client apps. I’ve found it works very successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vYY9McYvItokH37-." /><figcaption>Photo by <a href="https://unsplash.com/@bhaguz?utm_source=medium&amp;utm_medium=referral">Bagus Hernawan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Ready to launch your app?</h3><p>Here are a couple questions to ask yourself before you launch<br>1. What can you do post launch to gain a competitive edge?<br>2. How will crashes be managed, logged, fixed, tested, communicated to users.<br>3. How will performance be measured?<br>4. How will you improve and add new features? <br>5. How will you communicate to the new and exisiting user about new features?</p><p>The most important thing to remember is as long as your app is improving each app update and your users are happy you’re winning. So what are you waiting for, go out and start planning your marketing and post launch strategy.</p><p>That wraps up tips for launching your app.</p><p>It would mean the world to me if you shared or followed me on Medium. Have a great day :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fa16da1a530" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I have an app idea, now what?]]></title>
            <link>https://medium.com/@azzoor/i-have-an-app-idea-now-what-e760bc36a041?source=rss-802f18ee4183------2</link>
            <guid isPermaLink="false">https://medium.com/p/e760bc36a041</guid>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[app-idea]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[Aaron Stephenson]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 08:00:40 GMT</pubDate>
            <atom:updated>2018-03-06T13:32:23.861Z</atom:updated>
            <content:encoded><![CDATA[<p>Billion dollar apps are still appearing in the news and on your social feeds but has the app “gold rush” ended? Sure, gone are the days when you could just upload your app and wait for the users to download it. Now a days you need to think of your app more like running a business.</p><p>The good news is that people are still spending money on the App Store with Apple announcing on New Year’s day 2018 users collectively spent $300 million (in one day!!). In 2017 iOS developers earned $26.5 billion, more than 30% increase over 2016.</p><blockquote><em>“Genius: one percent inspiration and 99 percent perspiration.”, Thomas Edison</em></blockquote><p>Now that you have your idea that’s great, but you’ve only just completed 1% of the journey to your billion dollar app. Some of the things you need to think about include designing, accessibility, development, marketing (finding influencers, press releases), user feedback, customer support, user retention, pricing strategy (reoccurring payments vs pay once), building a community, web services, websites, plus much much more.</p><p>Now, lets talk about your idea. I’ll discuss some fundamental steps you need to complete to turn your idea into an app.</p><h3>What’s your problem?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZQ4vJKD5bFvuwIcg." /></figure><p>Your idea needs to solve a problem. If you want your app to be succesful it needs to move the needle in the positive direction. Otherwise you’re solving a problem no one has e.g. if it won’t add value to the world, then no one will use it better yet no one will pay for it.</p><p>A great way to determine if your idea is actually a valid problem solver is by validating it. Find a sample of your potential customers, survey them in person or online. Evaluate their responses, do more testing to refine your understanding of their wants and needs.</p><p>Some open ended questions to potentially ask are,</p><ol><li>What is the most difficult aspect of X (X is your problem or the area your problem relates to).</li><li>Tell me more about X.</li><li>What happened the last time X occured?</li><li>Why was the experience so problematic or unenjoyable?</li><li>How do you think X could be solved?</li></ol><p>The more you can learn about your potential customer pain points, the clearer picture you will have when it comes to creating your product and reduce scope creep. I find writing all these pain points on a whiteboard or on flash cards vital when designing my apps. This way when 1000’s of ideas on how the app should work and extra features are suggested you can ask yourself how would feature Y help solve pain point Z.</p><h3>Research the market</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fK3zP8ah36ka9aJJUSUqoA.jpeg" /></figure><p>At this point you’ve validated your customer problem with real world customers and have a clear idea of their pain points.</p><p>Search the App Store, is their already someone in the space of your problem? Don’t get discouraged, its often a good thing, it means there might be a market and users ready for someone to come in and “disrupt” it. When I say “disrupt” it could be your competitor isn’t taking advantage of new technology or oversight of customer pain points.</p><p>Analysing your competitors is a great way to get an insight into how they do things. Learning how your competitors:</p><ol><li>Are charging users? How much?</li><li>How often do they charge users?</li><li>Where they are marketing? Twitter, Facebook, Youtube, Print etc.</li><li>Who are they targeting in their marketing? Read the tone of voice is it targeting a gender, demographic?</li><li>Where are they marketing?</li><li>Search social media, who is commenting on the product pages or talking about the product.</li></ol><p>These are all valuable insights into how your competitors are doing things. You might find that your target user is actually different to who you originally thought and thus you need to focus on marketing differently or on a different platform.</p><h3>Find a Co-Founder</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*arlai_W6bQla4DYw." /></figure><p>I know what you’re thinking Elon Musk or Mark Zuckerberg didn’t have co-founders. Why do I need one? Many high growth startups are in fact the product of 2 or more co-founders.</p><p>Going back to my things you need to think about, that’s alot for one person to do. It’s not only going to delay your launch but you will be so rushed you’ll make mistakes. Having a co-founder allows you to share the responsibilities and workload.</p><p>Make sure you come to an agreement on the following items.</p><ol><li><strong>Define role responsibilities</strong> by collectively determining which tasks will belong to each co-founder.</li><li><strong>Create and sign a founders agreement</strong> to officially commence duties, equity ownership and vesting, and intellectual property assignments.</li><li><strong>Agree to time commitments</strong>, creating clear expectations regarding how much each co-founder will contribute, when and where is vitual to reduce friction in the long run.</li><li><strong>Decide on an exit plan</strong> rather then leaving unanswered key questions concerning what each member ultimately wants to do with the app.</li><li><strong>Agree on a “we failed” plan</strong>, if you decide early on you’ve failed or at some point want to move on from the company then both agree on the actions needed to resolve.</li></ol><p>With your co-founder(s), your researched problem and potential customer pain points in hand its finally time to build your MVP.</p><h3>Build and test your MVP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p9fGePqhVJmPvZrW." /></figure><p>Now it’s time to build your minimum viable product (MVP). A MVP is a stripped down version of your app, it’s the essentials only. This version of your app will be released to a limited group of people. Your MVP will give you hands-on, real world feedback from actual users.</p><p>Building your MVP and getting it into the hands of your testers forces you to ask and answer important questions:</p><ol><li>What makes people want to use the app?</li><li>What are the must have features vs the nice to haves (referr to your users pain points.)</li><li>Which features must be included in version 1.0 and which can I leave for a later date (future version).</li></ol><p>The thing to keep in mind when it comes to MVP is that the more “must have” version 1.0 features you add the more complex your app will become and the longer it will take to build. Stay focused on developing and releasing your MVP so that you can start gathering crucial feedback from actual users as soon as possible.</p><p>The most common issue I find with my startup clients is they are always wanting “just one more feature” which in turn makes the app so complex it’s no longer an MVP, its taken double the time to get something developed and once something is released they get feedback and its not what customers want or need.</p><p>That wraps up some fundamental steps you need to turn your idea into an app. I’ll be posting more each week.</p><p>It would mean the world to me if you shared or followed me on Medium. Have a great day :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e760bc36a041" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>