We share personal stories, talk about lessons we
learned and discuss topics that excites us about
digital products development.
Is it possible to develop a good product cheap and fast? In short: no. But some sacrifices are bigger than others.
When building a product, it’s easy to get carried away adding feature upon feature. So how to tame the feature creep and prioritize functionalities?
Style doesn’t have to cost the earth. Find out how we built LiveRobe’s minimum viable product to validate the sustainable startup idea and what should come next.
Like it or not, performance reviews are here to stay. We’ve rolled out a new competency-based, P2P-evaluation system. Read the lessons we’ve learned.
How and how much to charge when selling your expertise? At Digital Natives, we swear by time and material-based pricing. Here’s why.
Developing a viable product is not an easy ride, and we learned that the hard way in the past. See our blog post on the products we failed to bring to success and the lessons we learned from that.
In our last post we said that there is no such thing as “bugless” software. But in this case another question pops up: who to blame – and who to charge – when a software needs fixing?
Let’s face it: when you’re in the business of delivering digital solutions, bugs are all part of the process. They’re inevitable. But are all bugs created equally important?
Creating a mobile banking app with 148 screen designs in just 3 months sounds pretty impossible. And yet, this is what actually happened.