But wait, what about hybrid solutions for both platforms, e.g. As not all of them would have an iPhone available, Android was the natural choice. Eventually, I reasoned, this app would be in the hands of tour operators and guides all around the world. The War of the Worlds: Android vs iPhoneĪndroid or iPhone? This was an easy decision. In the following, I will explain some of my decisions in detail. There it was: My chance to start something from the ground up, making all the difficult decisions without becoming the most hated guy in the team. At that point, we only had a ticketing app (created during a hackathon), so it was clear to us that a proper supplier app would ultimately help to amaze our customers with great and seamless travel experiences. In the beginning of 2017, the mobile team at GetYourGuide decided to empower our tour suppliers with an improved app. What happens, though, if it’s your turn to make the decisions? How do you avoid being “the guy who created the thing”, that is, the person who is usually blamed for all the poor decisions on your project? I’ve been a programmer for about twelve years now, and can no longer count how often I’ve had to deal with somebody else’s decisions. A simple design decision can cause problems years later. Legacy is one of the major aspects a developer needs to consider when choosing between implementations, patterns, libraries - all sorts of these things. Guilherme Holz, Android Engineer in our Mobile Team, writes about how to make the right choices before starting a software project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |