You are in a discussion with a customer around the implementation of Google Maps APIs into their solution and, while asking some technical discovery questions, you find that a client wants to build an application from the ground up and will not be retrofitting an existing system. Why is this important to know for a Google Maps Platform implementation?
- Building an application from the ground up has more predefined constraints.
- Developing a new application from the ground up has significant time and financial impacts. Therefore, it is almost always a great deal cheaper, in time and money, to retrofit their existing solution with Google Maps Platform features.
- Usually, retrofitting has very little constraints, which will save the customer money if implemented. Therefore, there is less resistance to change.
- Typically, retrofitting brings with it a set of predefined constraints, which have time and financial impacts if changed. This means that designing an entirely new solution is actually cheaper in time and money than retrofitting their existing one.