Currently there is an onTouchListener setup on the AlarmEdit page which waits for user to edit the alarm name field. If it is the first time editing it, the field is cleared and waits for input. However, the issue arises here with getting the keyboard to move away from the screen following input.
Ideally, to make this intuitive, after the user is done with input, it should remove the keyboard from the screen. In addition, as it does already, it is important that the field does continually erase itself if the user attempts to make edits.
Currently there is an onTouchListener setup on the AlarmEdit page which waits for user to edit the alarm name field. If it is the first time editing it, the field is cleared and waits for input. However, the issue arises here with getting the keyboard to move away from the screen following input.
Ideally, to make this intuitive, after the user is done with input, it should remove the keyboard from the screen. In addition, as it does already, it is important that the field does continually erase itself if the user attempts to make edits.