We help clients create authentic brand experiences that allow their customers to do something amazing in the real world.
We’ve launched hundreds of consumer-facing digital experiences over the years, and continue to support some of the biggest and most successful products in New Zealand.
MVP’s (or minimum viable products) are often thought of as something you build once. But we believe products need to be iterative. And that means starting small and building from there.
We’ve learnt that sometimes projects fail because they try to deliver everything all at once.
But an MVP mindset challenges you to only build what is really important and necessary. Work as fast as you can and learn from every release and you will find that maybe you don’t need to build the product you thought you did.
We use the skateboard diagram above to illustrate this mindset. You think your end game is to build a car to transport yourself from A to B. But building all the parts required is going to take a long time. It’s only once you’ve built the entire solution that you can actually get from A to B. Whereas if you build the smallest possible solution – the skateboard – you’ve now invested far less time and effort but have a viable way to get from A to B.
And you may actually find that your users are satisfied with just the skateboard. Or you may realise that you don’t need a skateboard or a land vehicle at all, but a boat! Either way, you’ve saved yourself valuable time and budget by not trying to build that car from the start. And that’s why we will always work in an MVP mindset.
Native apps are built for specific platforms and are written in languages that the platform accepts. Both Apple and Google provide app developers with their own development tools, interface elements, and SDK.
A native app offers a great user experience, better performance and accessibility, delivering a more personalized product which is why PaperKite have historically specialised in this area.
Progressive web apps
Progressive web apps (PWA’s) are built to run inside a web browser and are hosted in a server using the same technology used in websites.
A PWA can be straightforward and quick to build. PWA’s need to be kept very simple and don’t offer the same features a native app can deliver.
A hybrid app is a combination of a native app and a web app. Hybrid apps don’t need a web browser because they use a native shell to run. This shell can be a webview or an app engine inside a native application.
Hybrid apps have access to a device’s internal APIs and device hardware and only one codebase is needed. However the key is to keep any customisation to a minimum otherwise you lose the benefits hybrid apps have to offer.
A self-organizing team has the ability to establish their own methodology or way of working together. That specific methodology should be built on top of a shared set of values and principles.
The key idea here is the team is able to craft their way of working that accounts for their context, their collective skill sets, the nature of work they are trying to do while considering any valid organizational constraints.