Our Philosophy On Apps


Strategy Lead Development

The first question is always why. Once we know the why, we can ask what. Only then can we work out how.


Less is more

Each additional button exponentially increases the complexity of an app. See Don't Make Me Think.


KISS Principle

Keep It Simple, Stupid. Most systems work best if they are kept simple rather than made complex.


User Experience

Focus on user experience the most important determinant of success in application adoption.


There's a time & a place

There are unique aspects to apps App vs Mobile Website. You need to know when to use each.


Start with an M.V.P.

Minimum Viable Product. Make sure your app achieves its primary aim. Iterate from there.


Think twice, Build once

If not conceived in planning, it generally takes 10 times longer to change or add a feature during the build.


Know the technology

An efficient build requires understanding the cost benefit trade-offs inherent in technology. We know the technology.


Working With Slay - Typical Process

This is the typical process we follow. We recognose that no two projects are alike and hence we remain flexible.

  1. Brief

    We ask that you complte our "Brief Form" before we meet. It should take 5-10 minutes. It helps everyone get on the same page and makes the first meeting more productive.

  2. Meet

    We meet face-to-face for 45 minutes. Agenda: Overview of Slay (10 minutes), Your background and why we should work together (10 minutes), What your project is (20 minutes), Next steps (5 minutes).

  3. Concept

    Based on our initial meeting, we often have to undertake some market and/or technical research. We will then form a number of concepts that we will package into a proposal.

  4. Quote

    We will meet again to discuss the concepts and provide you with ballpark costs. Once the final direction is established more detailed costing can be calculated. This generally occurs 10 days after the initial meeting.

  5. Design

    Aesetics and user experience are vitally important to the success of mobile applications. We will provide storyboards of user-flows and design key user experiences.

  1. Specify

    We will create a "Functional Spcifications" document that outlines we needs to be built and how we will build it. Our team uses it so we know exactly what to build, and you will know exactly what you are getting.

  2. Build

    We will suggest a number of milestones during the build process. We will undertake weekly WIP (Work In Progress) meetings so you can see exactly how we are tracking.

  3. Test

    After extensive internal testing, we will provide the app to you and your team to test. This is a time consuming yet vital part of the app development process.

  4. Launch

    This involves uploading website and submitting to the various app stores. Generally it takes 5-7 days to go through the Apple approval process. There is no approval process for Google Play.

  5. Maintain

    The app is not finished upon launch. Successful apps are continually improving, and performance is continually monitored. This is an ongoing process that Slay can help you with.


Our Requirements of Partners

Demonstrate a commitment to success. We want to work on successful projects.
Realise that an app is not set'n'forget. A successful app needs continued attention.
Know that Kevin Costner was wrong. Build it and they will NOT come. Apps need to be promoted.
Be a good person/company. Life is too short to work with people you don't like, so we won't.
Understand stuff breaks. There are many moving and interrelated parts. Parts can break.
Appreciate Software Development. It is often incredibly complex, and hard to predict.
Don't expect it to work on every Android. There are so many different varieties.
Be organised and responsive. Timely communication is key to an efficient build.
Be reasonable. Things never go 100% according to plan. Beware.

Technology Stack

tech stack

Simplicity is the ultimate form of sophistication.

— Leonardo da Vinci