Android ViewFlipper simplifies screen transitions by flipping between child views programmatically. When you need to display a specific child at a precise moment, combining setDisplayedChild with index-based logic and optional animations keeps the interface responsive and predictable.
Use ViewFlipper when you want a container that shows one view at a time and allows swipe or code-driven navigation. Direct index control gives you exact precision over which screen the user sees.
| Property | Description | Default | Typical Use |
|---|---|---|---|
| android:inAnimation | Animation resource applied when showing a new child | nullDefine enter transitions for smoother UX | |
| android:outAnimation | Animation resource applied when hiding the current child | nullCoordinate exit effects for consistency | |
| displayedChild | Index of the child view to show | 0 | Control current screen with setDisplayedChild |
| flipInterval | Auto-advance delay in milliseconds | 0 (disabled) | Enable automatic rotation carefully |
Set Displayed Child by Index
Use setDisplayedChild(int)
Call viewFlipper.setDisplayedChild(index) to immediately show a specific child. The index must be zero-based; otherwise, an IndexOutOfBoundsException may occur. Use this method when your flow requires instant jumps between screens without animation or with a predefined transition.
Validate Index Before Flipping
Check index range inside your logic to avoid crashes. A simple if condition ensures the target child exists, especially when data sets change dynamically. This guards against runtime errors in complex activities or fragments.
Show Child with Animation
In and Out Animation Setup
Assign android:inAnimation and android:outAnimation in XML or via code to make transitions visually clear. Built-in animations like slide_in_left and fade_out give a polished experience. Consistent motion helps users understand navigation context.
Show Specific Child with Animation
Use setDisplayedChild(index) together with animation resources to maintain fluid motion. The framework applies outAnimation to the current view and inAnimation to the new one. Keep durations short to prevent perceived lag on low-end devices.
Control Flow and Timing
Avoid Conflicting Calls
Sequential calls to setDisplayedChild can overwrite each other if triggered too rapidly. Debounce user actions and disable controls during ongoing animations. Synchronizing input events with view state prevents visual glitches.
Handle Configuration Changes
Retain the current index in onSaveInstanceState to preserve screen state across rotations. Recreate ViewFlipper children in onCreate to match the saved position. This keeps navigation intuitive after configuration changes.
Best Practices and Recommendations
- Use zero-based indexing to match your view list order
- Validate index ranges against getChildCount before flipping
- Apply consistent in and out animations for clear navigation
- Persist the current index across configuration changes
- Debounce rapid user actions to avoid conflicting calls
FAQ
Reader questions
How do I display child number 2 instead of child 0?
Call viewFlipper.setDisplayedChild(2) after the layout is ready, typically in onResume or after post layout checks. Ensure your ViewFlipper has at least three children to avoid index errors.
Can I show a specific child with a custom animation?
Yes, load animation resources and assign them to android:inAnimation and android:outAnimation, then use setDisplayedChild to trigger the transition. This gives you full control over motion while targeting the exact child index.
What happens if I set an out-of-bounds index in ViewFlipper?
The app throws IndexOutOfBoundsException and may crash unexpectedly. Always validate the index against getChildCount before calling setDisplayedChild to keep the UI stable.
How can I keep the displayed child after screen rotation?
Store the current index in onSaveInstanceState and restore it in onCreate, then call setDisplayedChild with the saved value. Combine this with stable view IDs for robust state preservation.