Most of us who have delivered more than one app know that the majority of these turn into applications. That transition from ‘app’ to ‘application’ brings new challenges from the initial prototype and deliver process. Adding all of those extra features requires us to slow down our velocity a bit to test all of the new inter-connectivity. In this post I want to share with you my perspectives on what it means to transition an ‘app’ into an ‘application’.
Sometimes these pesky development bugs just won't go away. I stepped back from the trees to look at the forest and try to find some commonality between the multiple applications I've worked on and the cause of the bugs found. Surprisingly I found more in common than I anticipated. Here's a few reasons why bugs exist in your applications and what you can do during development to avoid them.
One thing that is inevitable in software development is that you will create bugs in your software. The question becomes how and when you deploy fixes for them. Each client has differing levels of change control processes that need to be considered when dealing with these fixes. You want to eradicate the bugs as quickly as possible, particularly if they are preventing the end users from completing their work, but you don't want to affect current main line development. I'll give you a process I use that seems to be working best after much trial and error.