Reactive 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 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. In stage5, the status of the project is represented on the Kanban board, as captured in the following snapshot:

Figure 2.3: GitHub project Kanban board

We’ll implement the Add city search capability card (which captures a user story...