useState로 컴포넌트 상태 관리하기
useState 훅을 소개하고 카운터 또는 전환 값을 상태에 저장하며 상태 설정 함수를 호출해 다시 렌더링을 실행합니다.
useState로 컴포넌트 상태 관리하기은(는) CoddyKit의 무료 React Native Academy 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 React Native Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
What Is State?
State is data that can change over time and that a component owns and manages internally. Unlike props (which come from the parent and are read-only), state is created and updated by the component itself. When state changes, React automatically re-renders the component to reflect the new values in the UI. Common state examples include: whether a modal is open, the text the user has typed, the currently selected tab, or items fetched from an API. State is what makes React components interactive.
import { View, Text, TouchableOpacity } from 'react-native';
import { useState } from 'react';
export default function Counter() {
// Declare state: count starts at 0
const [count, setCount] = useState(0);
return (
<View style={{ padding: 24, alignItems: 'center' }}>
<Text style={{ fontSize: 48, fontWeight: 'bold' }}>{count}</Text>
<TouchableOpacity
onPress={() => setCount(count + 1)}
style={{ marginTop: 16, padding: 12, backgroundColor: '#4f86f7', borderRadius: 8 }}
>
<Text style={{ color: '#fff', fontSize: 18 }}>Increment</Text>
</TouchableOpacity>
</View>
);
}The useState Hook Signature
useState is a React Hook that you call at the top level of your component function. It takes one argument — the initial state value — and returns an array with two elements: the current state value and a setter function. You destructure these using array destructuring. The naming convention is [value, setValue]. The setter function is what you call to update state — never mutate the state variable directly. Each state variable is independent; call useState multiple times for multiple pieces of state.
import { useState } from 'react';
function MyComponent() {
// Syntax: const [value, setter] = useState(initialValue);
const [count, setCount] = useState(0); // number
const [name, setName] = useState(''); // string
const [isVisible, setIsVisible] = useState(false); // boolean
const [items, setItems] = useState([]); // array
const [user, setUser] = useState(null); // object or null
// Update state by calling the setter:
// setCount(5); ← sets to 5
// setName('Alice'); ← sets to 'Alice'
// setIsVisible(true); ← sets to true
}State Updates Trigger Re-Renders
When you call a state setter, React schedules a re-render of the component. During the next render, useState returns the new value. React is smart about this — it batches multiple state updates that happen in the same event handler and does a single re-render. Also important: the state value inside the current render is immutable. Calling setCount(count + 1) does not immediately change count in the current function execution — the new value appears in the next render cycle.
import { useState } from 'react';
import { View, Text, TouchableOpacity } from 'react-native';
export default function Example() {
const [count, setCount] = useState(0);
function handlePress() {
// These do NOT stack: count is still 0 in this render
setCount(count + 1); // schedules count = 1
setCount(count + 1); // also schedules count = 1, not 2!
// To correctly base on previous value, use functional update:
// setCount(prev => prev + 1); // prev = 0, result = 1
// setCount(prev => prev + 1); // prev = 1, result = 2
}
return (
<TouchableOpacity onPress={handlePress}>
<Text>{count}</Text>
</TouchableOpacity>
);
}Functional Updates with Previous State
When your new state depends on the previous state, always use the functional update form: setState(prev => prev + 1). React guarantees that prev is the most recent state value, even if multiple updates are batched. This is critical when incrementing counters, toggling booleans, or adding items to arrays in rapid succession (e.g., fast button taps). The object literal form (setState(state + 1)) can produce bugs when multiple updates happen before the component re-renders.
import { useState } from 'react';
import { View, Text, TouchableOpacity } from 'react-native';
export default function SafeCounter() {
const [count, setCount] = useState(0);
function increment() {
// Safe: uses previous state, handles batching correctly
setCount(prev => prev + 1);
}
function decrement() {
setCount(prev => Math.max(0, prev - 1)); // min 0
}
function reset() {
setCount(0); // direct value ok when not based on previous
}
return (
<View style={{ alignItems: 'center', gap: 12, padding: 24 }}>
<Text style={{ fontSize: 48 }}>{count}</Text>
<TouchableOpacity onPress={increment}><Text>+</Text></TouchableOpacity>
<TouchableOpacity onPress={decrement}><Text>-</Text></TouchableOpacity>
<TouchableOpacity onPress={reset}><Text>Reset</Text></TouchableOpacity>
</View>
);
}Toggling Boolean State
A very common pattern is toggling a boolean state between true and false. Use the functional update form with the logical NOT operator: setIsOpen(prev => !prev). This is cleaner than setIsOpen(!isOpen) because it correctly handles rapid presses. Common use cases include showing/hiding a modal, expanding/collapsing an accordion section, switching between play and pause, or toggling a favorite star icon. Booleans are perhaps the most frequently used type of component state.
import { useState } from 'react';
import { View, Text, TouchableOpacity, Modal, StyleSheet } from 'react-native';
export default function ToggleModal() {
const [isVisible, setIsVisible] = useState(false);
return (
<View style={styles.container}>
<TouchableOpacity
style={styles.btn}
onPress={() => setIsVisible(prev => !prev)}
>
<Text style={styles.btnText}>Toggle Modal</Text>
</TouchableOpacity>
<Modal visible={isVisible} transparent animationType='fade'>
<View style={styles.overlay}>
<Text style={styles.modalText}>Hello from the modal!</Text>
<TouchableOpacity onPress={() => setIsVisible(false)}>
<Text style={{ color: '#fff', marginTop: 16 }}>Close</Text>
</TouchableOpacity>
</View>
</Modal>
</View>
);
}
const styles = StyleSheet.create({
container: { flex: 1, justifyContent: 'center', alignItems: 'center' },
btn: { padding: 12, backgroundColor: '#4f86f7', borderRadius: 8 },
btnText: { color: '#fff', fontWeight: 'bold' },
overlay: { flex: 1, backgroundColor: 'rgba(0,0,0,0.7)', justifyContent: 'center', alignItems: 'center' },
modalText: { color: '#fff', fontSize: 20, fontWeight: 'bold' },
});State with Strings: Controlled Text Input
Binding a TextInput to state creates a controlled input. The value prop sets the displayed text (from state), and the onChangeText callback updates the state whenever the user types. This makes the state the single source of truth for the input's value — you can read, validate, or transform the text at any time by reading the state variable. Without binding to state (uncontrolled), you would need a ref to read the input value, which is less idiomatic in React.
import { useState } from 'react';
import { View, Text, TextInput, StyleSheet } from 'react-native';
export default function SearchBox() {
const [query, setQuery] = useState('');
return (
<View style={styles.container}>
<TextInput
value={query}
onChangeText={setQuery} // same as: (text) => setQuery(text)
placeholder='Search...'
style={styles.input}
/>
<Text style={styles.preview}>
You typed: <Text style={{ fontWeight: 'bold' }}>{query}</Text>
</Text>
<Text style={styles.count}>{query.length} characters</Text>
</View>
);
}
const styles = StyleSheet.create({
container: { padding: 16, gap: 8 },
input: { borderWidth: 1, borderColor: '#ccc', borderRadius: 8, padding: 12, fontSize: 16 },
preview: { fontSize: 14, color: '#555' },
count: { fontSize: 12, color: '#999' },
});State with Arrays: Adding and Removing Items
When state is an array, never mutate it directly with push or splice. Instead, create a new array with the change and pass it to the setter. To add an item: setItems(prev => [...prev, newItem]). To remove an item: setItems(prev => prev.filter(item => item.id !== id)). To update an item: setItems(prev => prev.map(item => item.id === id ? {...item, done: true} : item)). These immutable patterns let React detect changes and schedule efficient re-renders.
import { useState } from 'react';
import { View, Text, TouchableOpacity, TextInput, FlatList } from 'react-native';
export default function TodoList() {
const [todos, setTodos] = useState([]);
const [input, setInput] = useState('');
function addTodo() {
if (!input.trim()) return;
setTodos(prev => [...prev, { id: Date.now().toString(), text: input.trim(), done: false }]);
setInput('');
}
function toggleDone(id) {
setTodos(prev => prev.map(t => t.id === id ? { ...t, done: !t.done } : t));
}
return (
<View style={{ flex: 1, padding: 16 }}>
<TextInput value={input} onChangeText={setInput} placeholder='Add a todo' />
<TouchableOpacity onPress={addTodo}><Text>Add</Text></TouchableOpacity>
<FlatList
data={todos}
keyExtractor={t => t.id}
renderItem={({ item }) => (
<TouchableOpacity onPress={() => toggleDone(item.id)}>
<Text style={{ textDecorationLine: item.done ? 'line-through' : 'none' }}>
{item.text}
</Text>
</TouchableOpacity>
)}
/>
</View>
);
}State with Objects
For related pieces of state, group them into a single object state variable. When updating object state, spread the previous state to keep unchanged fields: setState(prev => ({ ...prev, name: 'Alice' })). This only overwrites the name field while keeping all other fields intact. Alternatively, each field can be its own useState — neither approach is universally better. Use an object when the fields always change together (like a form with name, email, and password); use separate states when they change independently.
import { useState } from 'react';
import { View, TextInput, Text, StyleSheet } from 'react-native';
export default function ProfileForm() {
const [form, setForm] = useState({
name: '',
email: '',
bio: '',
});
function updateField(field, value) {
setForm(prev => ({ ...prev, [field]: value }));
}
return (
<View style={{ padding: 16, gap: 12 }}>
<TextInput
value={form.name}
onChangeText={v => updateField('name', v)}
placeholder='Name'
style={styles.input}
/>
<TextInput
value={form.email}
onChangeText={v => updateField('email', v)}
placeholder='Email'
style={styles.input}
/>
<Text style={{ color: '#666' }}>Preview: {form.name} — {form.email}</Text>
</View>
);
}
const styles = StyleSheet.create({
input: { borderWidth: 1, borderColor: '#ccc', borderRadius: 8, padding: 12 },
});Lazy Initial State
If computing the initial state is expensive (reading from AsyncStorage, parsing a large dataset), pass a function to useState instead of a value: useState(() => computeExpensiveValue()). React calls this initializer function only once on the component's first render, not on every subsequent render. This is called lazy initialization. Passing an expensive computation as a plain value (useState(expensiveCompute())) would run it on every render, causing unnecessary work even though the initial state is only used once.
import { useState } from 'react';
// Without lazy init: computeExpensiveList() runs on EVERY render
const [list, setList] = useState(computeExpensiveList()); // BAD
// With lazy init: function is called ONCE on mount
const [list, setList] = useState(() => computeExpensiveList()); // GOOD
// Real example: JSON.parse is cheap, but still good practice:
const [settings, setSettings] = useState(() => {
const stored = SomeStorage.get('settings');
return stored ? JSON.parse(stored) : { theme: 'light', lang: 'en' };
});Derived Values vs. Redundant State
Don't store values in state if they can be derived from existing state or props. For example, if you have a list of todos in state, don't also store a completedCount in state — compute it as todos.filter(t => t.done).length during render. Storing derived values in state creates synchronization bugs: you forget to update one when you update the other. Only put things in state that you can't derive, can't compute during render, or that are asynchronously set (like API response data). This rule keeps state minimal and bug-free.
import { useState } from 'react';
import { Text, View } from 'react-native';
export default function TodoStats() {
const [todos, setTodos] = useState([
{ id: '1', text: 'Buy groceries', done: true },
{ id: '2', text: 'Write code', done: false },
{ id: '3', text: 'Go for a walk', done: true },
]);
// DERIVED: computed from existing state, not stored in state
const total = todos.length;
const completed = todos.filter(t => t.done).length;
const remaining = total - completed;
return (
<View style={{ padding: 16 }}>
<Text>Total: {total}</Text>
<Text>Completed: {completed}</Text>
<Text>Remaining: {remaining}</Text>
</View>
);
}useState vs useRef: When Not to Use State
Not every value that changes in a component needs to be in state. If a value changes but does not need to trigger a re-render, store it in a useRef instead. Common examples: a timer ID returned from setTimeout, a flag tracking whether a network request is in flight, or the previous value of a prop. Putting these in state causes unnecessary re-renders. A useRef persists its value across renders (like state) but updating it does not schedule a re-render. The golden rule: if the UI doesn't need to change when the value changes, use useRef.
import { useState, useRef, useEffect } from 'react';
import { Text, TouchableOpacity, View } from 'react-native';
export default function Timer() {
const [elapsed, setElapsed] = useState(0);
const intervalRef = useRef(null); // timer ID in ref — no re-render needed
function start() {
if (intervalRef.current) return; // already running
intervalRef.current = setInterval(() => {
setElapsed(prev => prev + 1); // state — needs re-render to show
}, 1000);
}
function stop() {
clearInterval(intervalRef.current);
intervalRef.current = null;
}
useEffect(() => () => clearInterval(intervalRef.current), []); // cleanup
return (
<View style={{ alignItems: 'center', padding: 24, gap: 16 }}>
<Text style={{ fontSize: 48 }}>{elapsed}s</Text>
<TouchableOpacity onPress={start}><Text>Start</Text></TouchableOpacity>
<TouchableOpacity onPress={stop}><Text>Stop</Text></TouchableOpacity>
</View>
);
}Quick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: useState declares state variables and provides a setter that triggers re-renders, functional updates safely derive new state from the previous value, and derived values should be computed during render instead of stored as redundant state. Next up we explore lifting state up to share data between sibling components.
자주 묻는 질문
“useState로 컴포넌트 상태 관리하기” 강의는 무료인가요?
네 — “useState로 컴포넌트 상태 관리하기” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 React Native Academy 강의 전체를 잠금 해제할 수 있습니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
“useState로 컴포넌트 상태 관리하기”에서 뭘 배우나요?
useState 훅을 소개하고 카운터 또는 전환 값을 상태에 저장하며 상태 설정 함수를 호출해 다시 렌더링을 실행합니다. 브라우저에서 직접 실행하는 실습 코드로 React Native Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
React Native Academy을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 React Native Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“useState로 컴포넌트 상태 관리하기” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 React Native Academy 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 React Native Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- Props로 데이터 전달하기
- useState로 컴포넌트 상태 관리하기
- 상태 끌어올리기
- 대화형 카운터 앱 만들기