When we talk about wireframes, mock-ups, and prototypes, we are talking about graphical representations of software - how a system will look to end-users - and, in the case of the prototype, how it will work, too. This is generally in the form of an app (whether web, mobile, or desktop), although you might get clever with things like IoT and smart watch displays, too.
What a time to be alive! When cars can (almost) drive themselves, our phones can unlock just by showing our face, and Siri can schedule meetings for us… Isn’t life grand? And easy? Machine Learning is seeping into our everyday lives - it’s not just operating behind the scenes in business helping banks spot fraudulent transactions, bolstering against enterprise cybersecurity attacks, and helping allocate and deallocate computing infrastructure for reduced operational costs.
Developing your own app is an important thing to get right, whether it’s for use within your own business, client-facing, or for the general public. One of the first decisions to make when developing an app is the choice whether to develop for the browser (web app), or for native use (downloaded to computer or mobile).
Software is full of either-or choices. Android or iOS, Agile or Waterfall, backend or frontend, AWS or Azure. One that we often get asked about is the difference between open-source and proprietary software.
There’s plenty of software-speak that goes whooshing over the heads of most people - and even some of the heads of those programming! Two of the terms that you might hear thrown about in the world of software are microservices and web services. These are both ways of defining software products: by breaking larger software products down into manageable chunks that can talk to each other. Let’s take a closer look.
For any business, not for profit, or even for building a personal project or your personal brand, embarking on web and app development can be a tricky time. Without personal experience in the process, it’s hard to figure out timelines: which should go where, and when?
Fixed price contracts can be rather tricky in a Scrum environment. Classic software development and Agile software development are very different from one another, and things that work in one environment don’t necessarily work in another.