Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. Like the tale of the three little pigs, software is often written in order to be released as soon as possible, regardless of the medium and long-term implications of those decisions.
The first thing to do when starting to design the interface of an mobile app is the definition of the size of the workspace. For example, Android recommends designing with a document prepared for a standard base, such that when preparing files for the developers, we can scaled for higher or lower densities (resolutions). On the opposite side is iOS, which recommends designing in resolution for retina screens, that is in the highest possible density.
The design and development process ranges from the conception of the idea to its subsequent publication in stores and an analysis of the results of use. At all times, designers and developers must work together, in an orderly manner, to meet the objectives of each stage. Let's see in this post the most important stages of this process.
The speed of technology force us to research for innovation constantly: without an update and a daily training we lose our competitive edge. So we try new techniques, we learn new programming languagues which resolve our business problems more efficiently. But we must not lose focus, otherwise you could end up developing an admirable app for a colleague, but an poor solution for our clients.