Reactive forms versus template-driven forms

Now, we'll implement the search bar on the home screen of the application. The next user story states Display forecast information for current location, which may be taken to imply an inherent GeoLocation functionality. However, as you may note, GeoLocation is listed as a separate task. The challenge is that with native platform features such as GeoLocation, you are never guaranteed to receive the actual location information. This may be due to signal loss issues on mobile devices or the user may simply refuse to give permission to share their location information.

First and foremost, we must deliver a good baseline UX and implement value-added functionality such as GeoLocation only afterward. Instead, let's move Add city search capability ... to In progress, as shown on our Kanban board:

Figure 6.2: GitHub project Kanban board

As part of this story, we are going to implement a search-as-you-type functionality...