Tag: validate

  • What can you do to reduce the cost of building an online platform or mobile app?

    What can you do to reduce the cost of building an online platform or mobile app?

    In my last article, I looked at some of the major things that can affect the cost of building an online platform or mobile app. This article is going to look at some of the ways you can reduce your initial costs, without severely compromising your idea and the quality of the final product.

    The most effective way to reduce costs is to look at the following:

    1. Build less
    2. Reduce complexity
    3. Build for fewer devices

    1. Build Less

    It might sound obvious, but it’s a very difficult thing to do. How do you do decide what to cut out and what to keep? Often everything will seem important, and you’ll have to make some though choices. The reality is – research has shown that 80% of functionality for custom-built applications isn’t used, so as it turns out, there might be some features and functions that you don’t need for your launch.

    There’s an important thing to note here. Building less doesn’t mean that you never build the rest of the things that you want. What it does mean is you pick the things that your potential customers and users really want. Once they start paying you, you can afford to build more. Building less has other advantages around minimising the riskiness of your project.

    2. Reduce Complexity

    This one is probably a difficult if you don’t have any technical knowledge. How are you going to know if something is complex or not? Where building less is about the number of features and functions, reducing complexity is about what goes into each feature and function. It includes taking out steps in a process, and minimising the choices and scenarios that are possible. Generally, it’s about getting the platform or app to do less in the way of processing and calculating.  By reducing complexity, there are fewer places where things can go wrong.  When things go wrong, you have to pay more money to fix them.

    3. Build for fewer devices

    As I mentioned in my previous article, the more devices you build for, the more it costs. While responsive design deals with some of the differences in screen sizes, there will be cases where there just might not be enough space on a mobile phone screen. This means that you may have to adjust your design for mobile devices, and that means more designing, more coding, and more testing. With tablets and phones, and even laptops, your developers will also have to consider interactions with a mouse versus a touch screen.

    Why should you look to keep your costs low?

    No one wants to spend more money than they need to. However, people often go to a developer with a laundry list of things to do, and then get surprised by the amount they’re quoted.

    You might find that to reduce your costs, you may only need to do some of the things above.  By spending less money upfront, you can use the extra dollars in valuable updates after your product has launched.

    The more compelling reason for reducing your costs is actually around the uncertainty of making the money back. The more money you spend, the more you have to sell to make your money back, and to ultimately become profitable.

    Even if your most pessimistic business plans show you making money, it’s worth going through this exercise to see where you can cut the fat.  This can only mean more money in your pocket, so what have you go to lose?

    Are you ready to turn your good idea into a great product?
    My idea to launch checklist is your plain-English guide to getting there.

    It’s available now for only $24.
  • How much does it cost to build an online platform or mobile app?

    How much does it cost to build an online platform or mobile app?

    Cost is a big factor with any investment, and software development is no different. So, how much does it cost to build an online platform or mobile app?

    The answer – it depends. You might be able to get away with $10,000 or it might cost you $200,000+.

    Yes, an infuriating and vague response, but unfortunately, very true.

    Think along the lines of “how long is a piece string?” Software development projects can be small or they can be big. This, of course, affects the cost.

    Factors that can affect cost

    There are many things that can affect the cost of software development. Here are some main ones:

    1. What features and functionality you want (and how complicated it is)
    2. Who will build it
    3. How it will be built
    4. What devices need to be supported

    Let’s look at each of these in more detail.

    1. What features and functionality you want (and how complicated it is)

    There is a direct correlation between how much you want to build and the cost. An app with 50 functions is going to cost more than an app with 10. It just takes longer to build more, than to build less.

    The next part of this relates to how complicated the functionality is. We might both define a product with 10 functions, but they may differ in complexity. Mine might have lots of different rules, require lots of information to be captured and stored, and need lots of calculations to be completed. Yours may just be displaying different types of content that has been loaded into the system. Mine will probably cost more to build.

    2. Who will build it

    It’s no secret that going offshore will get you a lower daily rate than staying onshore. You’re probably looking at a difference of $50-$75 per hour. This can add up over a large project. However, the quality may not be there.

    There is also a difference between using a freelancer versus an agency. Agencies have a lot more overheads to cover, which makes them more expensive, but they usually have better coverage of the end-to-end process, because they have staff to address all of the skill sets needed to build software.

    Another element is the experience of the developer. As expected, if you use someone with lots of experience, it’s going to cost a lot more than if you have an inexperienced one. The balancing act between cost and experience is a tough one. Depending on your budget, it may be worth the risk to give someone less experienced a chance. However, if you don’t have a lot of time to spend on the project, then you’ll need someone more experienced.

    3. How it will be built

    If you’re building a mobile app, then the question of native vs hybrid will often be raised. Native apps are built individually for each phone operating system (e.g. iOS vs Android), and in the language of those operating systems. On the other hand, a hybrid app will be built once, and then converted into apps for different operating systems. The former is much more expensive because you have to build the app multiple times, but it allows you to have a product that is made specifically for that operating system. Hybrid apps work well too – and are often a good starting point – but you have to compromise because you’re building a “one-size-fits-all” product.

    On the web side, there are lots of ways to build a platform. You can use existing platforms like Wordpress to build very functional and experience-rich applications. Or you can build from scratch. This approach can have varying costs too depending on what you want.  If you can leverage an existing platform, it’s probably going to be cheaper than building from scratch. However, down the line, you might have to replace it with something else that allows you to do all the things that you might want to do.

    4.What devices need to be supported

    The number of devices that you want to run your product on will also affect the cost. If you’re only looking at a platform that someone will use on a laptop or desktop, that’s a different proposition to having it work on all device types. Just dealing with multiple screen types adds lots of overheads. Think about the different sizes of mobile screens and you’ll start getting an idea of the effort involved. Even if your product is built to be responsive, you still have to test it on all of these devices to make sure it works as expected. If you want to support touch screens, then there’s even more stuff to design, build and test. A lot more work has to go into making your product work on multiple devices, than making it work on one.

    How much will your project cost?

    Hopefully, you’ve now got a better feel of some of the major things that affect the cost of a software project. There isn’t a standard number that someone can give you.  If you want to know how much you need to budget for, then you really need to talk to a few developers about your specific idea. They should be able to give you can indication of the cost. You also need to find out how different parts of your idea will affect the cost, and where you might be able to simplify things or reduce what you build. This might affect the viability of your idea.

    At the end of the day, you need to know what it’s going to cost to make your idea a reality. This also includes all of the other costs that you’ll incur to launch your product. To give yourself the best chance at success, make sure your budget can cover it all.

    Looking for a developer?
    Get my 10 Essential Tips for hiring the right developer for your project.
    Download it now for free!
  • Why should you build a prototype?

    Why should you build a prototype?

    Prototyping is a common approach for developing a mock or sample product to help test concepts before building out the real thing. It’s used in all different industries and can come in all shapes and forms.

    In this article, I’ll look at what a prototype looks like for online platforms and apps, and how it can help you build a better product.

    What is a prototype?

    A prototype is anything that represents your future product to a user. Traditionally, in manufacturing, this might have been a sample of a piece of clothing or something cobbled together to show how the product might work.

    Today, when it comes to platforms and apps, the approach is the same. You want to build something that represents your future product without actually building the whole thingdf.

    As software isn’t a physical product that you can create a sample of, the most popular way to prototype is to create something called a clickable prototype.

    What is a clickable prototype?

    A clickable prototype is a collection of medium or high-fidelity wireframes that represent what a customer might need to do to complete a task. These wireframes are put into a computer, where you add some ‘buttons’ and ‘links’ that allow people to navigate through your prototype.

    There are prototyping applications you can use, such as InVision, Balsamiq, and Acrobat XD, that provide a set of tools to help you build and get feedback on your prototype. You can also use something like PowerPoint or Keynote. Even some hand drawn pictures can work as well.  The video below gives you an example of what a prototype looks like.

    The main idea is that people have something to see and ‘hold’ in order to better understand what you want to do.

    So, when do you do all of this?!

    There are two main areas where you can use prototypes:

    1. Validate an idea
    2. Test your design

    1. Validate an idea

    If you find your idea is hard to explain to potential customers and users, then a prototype is a one way to illustrate what your platform or app will do. By building a prototype, you can get feedback on your idea, and get input into what you need to include in your product. You might find some features are more important than others, which might change the way you prioritise your app’s development.

    2. Test your design

    Prototypes are also good at testing your product’s user experience. The prototype represents how your users will navigate through your system. You want to find out which parts are easy to use, and which aren’t. By getting people to play with your prototype, you can identify how well the solution addresses their problems based on its usability.

    Why would you prototype?

    If used correctly, prototyping will give you a more informed idea of what you should be building, so that you can get people to use it. Prototyping will also allow you to build a better product, so that the people using it will keep using it.

    Ultimately, both of these things reduce the risk of you spending money unnecessarily. If you can’t build the prototype yourself, it will cost you some money. However, spending a small amount of money to discover you’re building the wrong thing is way better than spending months, and a lot more money building something that isn’t what you need.

    Are you ready to turn your good idea into a great product?
    My idea to launch checklist is your plain-English guide to getting there.

    It’s available now for only $24.
  • I have an idea for an app – what happens next? (idea validation)

    I have an idea for an app – what happens next? (idea validation)

    Getting a great idea for a new business venture is such an exciting feeling. Finally – you have something that might have legs but you’re still on the fence about what to do with it. It’s such a risk, but can you imagine the life that you might have – the flexibility of being your own boss and hopefully some financial rewards too? If you already run your own business, a new idea may allow you to grow your revenue and allow you to serve more customers.

    For some people, ideas are relatively easy to come by; for others, they struggle with coming up with just one.  However, it’s the ones that require you to build a web platform or mobile app that I’m interested in.

    There are many businesses that people can start and all of them have their complexities – if you want to design and make your own clothes, you’ll have to source fabric and manufacturing. If you want to sell other people’s goods, you’ll need to find those suppliers. If you want to be a consultant or service provider, you’ll have to decide what you want to offer and how you’ll deliver it.

    What makes developing an app particularly troublesome is the cost to build it.  Also, compared to physical goods, it’s not as easy to see a “sample” of your app before you put in the big order, which makes it difficult to know what you’re getting.     

    What should you do?

    If you’ve never been involved in an IT project before, an obvious question once you get your idea is – what do I do next? It’s a very smart question to ask! Before you quit your day job or bet the house on your new venture, let’s take a look at what your next steps should be. 

    If you read my first article on product and software development – you’ll know the answer to this question! 

    After you’ve come up with an idea, you need to analyse or validate it. This is the process of making sure that the idea is the right one to pursue. Making your idea a reality is going to require some investment from you – and it’s not only going to include your time.  More importantly, it’s going to include your money. Therefore, you need to take some time to research your idea to make sure the investment is worth it.

    Idea validation is a necessary step for most businesses, large and small – and it should be no different for you. The last thing you want to do is to spend money on an idea that no one wants. A structured approach to evaluating your idea is key. 

    So, what exactly are you looking for?    

    To get you started, we’ve put together five ways you can validate your idea:
    1. Talk to potential users – use your social media platforms to see if anyone knows anyone who has experienced the situation that you want to solve for, then ask them about their experiences and find out what their issues were. Determine if your product could solve their problems. Alternatively, start with a survey via SurveyMonkey or Typeform to get some feedback about your idea and then interview some of the people that responded.
    2. Look at your potential competition – use a search engine to see if there are any other companies currently doing what you want to do. Determine if what you could offer is at least as good, if not better, than what they do now. Also look at companies that solve the same problem but in a different way. Would you be able to stand out from the competition? 
    3. Look at potential environmental factors that may affect the viability of your business – are there new laws or regulations being proposed? Are there changes in technology? Are people behaving or thinking differently? A lot of new product successes are about timing rather than the product itself – if the world isn’t ready for it, it will be a lot harder to be successful regardless of how good the product is.
    4. Determine the potential size of your market – look for statistics that can give you an indication of the number of people that might experience the problem that you want to solve. What percentage of those people might buy your product?
    5. Think about how much you might charge for your product – would the price be one- off or recurring? Would there be an upsell or downsell? How could you get your customers to buy more from you? How many products would you have to sell to achieve your desired goals?
    What happens next?

    The above will give you an initial view of whether your idea is a good one. Sometimes this is enough for you to make a decision, but more often than not, you’ll have to dig a little deeper to gain the confidence that you need to go ahead with building your app. 

    There are lots of things to look at when validating an idea!  If you work for a large organisation, think about all of the processes that they put in place for spending money on new things.  People have to justify to the company why the idea is the right one to pursue.  

    It’s important to remember that you can’t take the risk out of every investment, but you do want to get enough information to make an informed decision about your idea.  After all, building an app could have a very big impact on your life  good or bad. So, the obvious is question it  why wouldn’t you take the time to validate your idea first?! 

    There are many different things to look at when validating an idea and different ways to do it. If you’ve gone through this process before, please feel free to share what you’ve done in the comments below.

    Want a blueprint for validating your idea?
    My Validation Course will walk you through some key tasks and activities to make sure your idea is worth pursuing

    It’s available now for only $47.

    * When you download a copy of our cheat sheet, we’ll also add you to our mailing list so you can receive emails from us (with your consent). These emails will include news and updates, occasional offers and promotions, and exclusive content and resources to help you on your development journey. You may also receive follow-up emails in relation to this download. We will not spam you. If you don’t wish to hear from us anymore, simply select the unsubscribe option at the bottom of any email that we send to you. To view our privacy policy, click here.