What is a FocusNode and why is it useful in forms?

WHAT THIS TESTS: The interviewer is probing whether you understand that Flutter's focus system is an imperative tree sitting alongside the widget tree, not a purely declarative construct. They want to see that you know FocusNode is a persistent ChangeNotifier representing a focus target, that it must be owned and disposed by a StatefulWidget, and that it is the mechanism for programmatically driving keyboard focus in forms. They also care if you recognize the difference between automatic management via Focus widgets and direct manual management, and when the latter is necessary.

A GOOD ANSWER COVERS: First, define FocusNode as a persistent object that forms part of the sparse focus tree used by the FocusManager to route key events. Second, explain its utility in forms: it lets you move focus between fields with FocusScope.of(context).requestFocus(nextNode), unfocus to dismiss the keyboard, and listen to hasFocus to update UI decoration. Third, cover lifecycle rigor: create the node in initState, attach it through a Focus widget or by passing it to a TextField focusNode parameter, and call dispose in State.dispose to avoid leaking listeners. Fourth, note that while Focus and FocusScope widgets manage nodes automatically, direct management is required when an ancestor needs to control descendant focus or when the widget subsystem is bypassed.

COMMON WRONG ANSWERS: Creating a FocusNode inside the build method is the most common critical error because it recreates the node on every rebuild and instantly drops keyboard focus. Forgetting to dispose the node is another serious leak because FocusNode is a ChangeNotifier. Some candidates incorrectly claim FocusNode is only for text inputs, when any widget can host one. Others say manual management is never needed, which ignores form traversal and custom keyboard handling. Finally, confusing FocusNode with FocusScopeNode or failing to mention FocusAttachment and reparenting shows shallow knowledge.

LIKELY FOLLOW-UPS: The interviewer might ask how to customize tab traversal order or restrict traversal to a group of nodes. They may ask how to intercept hardware key events via the onKeyEvent callback and how event bubbling works up the focus tree. Another angle is the difference between unfocus and requesting focus on another node, or how to debug the focus tree at runtime with debugDumpFocusTree. You might also be asked how FocusNode interacts with scrolling or how to handle focus in lists.

ONE CONCRETE EXAMPLE: Consider a registration form with name, email, and password fields. In a StatefulWidget, create three FocusNode fields in initState. Pass each node to its corresponding TextField via the focusNode parameter. Set the name field textInputAction to TextInputAction.next. In its onEditingComplete callback, call FocusScope.of(context).requestFocus(emailNode). Repeat from email to password. On the password field, set textInputAction to TextInputAction.done and call FocusScope.of(context).unfocus in onEditingComplete to hide the keyboard. In State.dispose, call nameNode.dispose, emailNode.dispose, and passwordNode.dispose. This pattern keeps focus state stable across rebuilds and gives precise programmatic control.