This document provides an introduction to lesson 5 on rich and responsive layouts. It discusses storing and displaying data, and being ready to build rich user interfaces that follow Android design principles. These principles include making apps look polished, professional, easy to use, fun, and providing simple shortcuts. The document also recaps the roles of views and view groups in handling drawing and events.

1. Lesson

2. 5.

3. Rich

4. and

5. Responsive

6. Layouts
도우미

7. 이찬형

8. Intro

9. to

10. Lesson

11. 5
•Store

12. the

13. data

14.
•display

15. the

16. data

17.
•We’re

18. ready

19. to

20. build

21. rich

22. UI

23. Android

24. Design

25. Principles(1)
•Users

26. judge

27. the

28. quality

29. of

30. your

31. app

32.
within

33. the

34. first

35. 30

36. seconds

37.
•judgement

38. will

39. be

40. based

41. not

42. on

43. the

44.
functionality,

45. but

46. on

47. the

48. visual

49.
aesthetics

50. Android

51. Design

52. Principles(2)
•look

53. polished

54.
•look

55. professional

56.
•easy

57. to

58. use

59.
•fun

60. to

61. use

62.
•short

63. and

64. frictionless

65.
•let

66. users

67. touch

68. and

69. interact

70. with

71. objects

72.
•rich

73. imagery

74. and

75. pictures

76.
•provide

77. simple

78. shortcuts

79. to

80. complete

81. complex

82. tasks

83. Enjoyable

84. Apps
•What

85. makes

86. your

87. favorite

88. apps

89. enjoyable

90.
to

91. use

92. ?

93. Recap

94. on

95. Views

96. and

97. ViewGroups(1)
•a

98. view

99. handles

100. drawing

101. and

102. event

103.
handling

104.
•text

105. field,

106. buttons,

107. drop

108. down

109. menu,

110.
checkboxes,

111. radio

112. button,

113. on/off

114. switch,

115.
progress

116. bar

117. Recap

118. on

119. Views

120. and

121. ViewGroups(2)
•A

122. view

123. group

124. is

125. a

126. container

127. for

128. children

129. views

130. Recap

131. on

132. Views

133. and

134. ViewGroups(3)

135. Recap

136. on

137. Views

138. and

139. ViewGroups(4)

140. Recap

141. on

142. Views

143. and

144. ViewGroups(5)

145. Recap

146. on

147. Views

148. and

149. ViewGroups(6)

150. Building

151. List

152. Item

153. Building

154. List

155. Item

156. Building

157. Todays

158. List

159. Item
•Use

160. the

161. same

162. place

163. holder

164. image

165.
•Use

166. the

167. same

168. IDs

169.
•SimpleCusorAdapter

170. only

171. supports

172. one

173.
item

174. view

175. types

176. Cursor

177. Adapter

178. •newView

179. method

180. knows

181. how

182. to

183. return

184. a

185.
new

186. list

187. layout,

188. but

189. doesn’t

190. contain

191. data

192.
yet

193.
•bindView

194. method

195. knows

196. how

197. to

198. take

199. an

200.
existing

201. layout

202. and

203. update

204. it

205. with

206. the

207. data
Cursor

208. Adapter

209. •getViewTypeCount

210. return

211. to

212. two

213. for

214. the

215. two

216. different

217.
layouts

218.
•getItemViewType

219. return

220. to

221. VIEW_TYPE_TODAY

222. or

223.
VIEW_TYPE_FUTURE_DAY

224.
•modify

225. newView

226. method

227.
•bindView
Two

228. Item

229. View

230. Types

231. •To

232. remove

233. unnecessary

234. findViewById

235. calls,

236.
we

237. can

238. use

239. the

240. View

241. Holder

242. Pattern

243.
•Set

244. the

245. ViewHolder

246. as

247. the

248. tag

249. of

250. the

251. view
Using

252. the

253. viewHolder

254. Pattern

255. •날짜

256.
•온도

257.
•http://kakaoplus.tistory.com/68
Formatting

258. Strings

259. Coding

260. the

261. Details

262. Screen
•Break

263. up

264. the

265. UI

266. into

267. smaller

268.
components

269.
•Move

270. DetailFragment

271. to

272. new

273. file

274. Coding

275. the

276. Details

277. Screen

278. Optimizing

279. Layouts
•Inflating

280. complex

281. layouts

282. can

283. be

284.
expensive

285.
•keep

286. your

287. layout

288. shallow

289. and

290. wide,

291.
rather

292. than

293. deep

294. and

295. narrow

296. Hierarchy

297. Viewer

298. Responsive

299. Design
•What

300. does

301. it

302. look

303. like

304. on

305. the

306. tablet

307.
•Combining

308. multiple

309. views

310. into

311. One

312.
•It’ll

313. be

314. used

315. across

316. a

317. range

318. of

319. different

320.
device

321. screen

322. sizes

323. Splitting

324. Devices

325. into

326. Buckets
•http://www.kmshack.kr/%EC%95%88%EB%93%9C%EB%A1%9C%EC%9D%B4%EB%93%9C-%EC%95%B1-%EA%B0%9C%EB

327. Resource

328. Folder

329. Qualifiers
•The

330. Android

331. resource

332. framework

333.
•Android

334. allows

335. you

336. to

337. create

338.
alternative

339. versions

340. of

341. every

342. resource

343.
by

344. placing

345. them

346. into

347. folders

348. with

349.
different

350. qualifiers

351. Resource

352. Folder

353. Qualifiers

354. Images

355. for

356. Different

357. Densities

358. Adding

359. Images

360. to

361. the

362. App

363. Tablet

364. UX

365. Mocks

366. Why

367. Do

368. we

369. Need

370. Fragments
•Allow

371. us

372. to

373. fully

374.
modularize

375. our

376.
activities

377.
•Fragments

378. were

379. first

380.
introduced

381. in

382.
Honeycomb

383. to

384. solve

385. a

386.
particular

387. problem

388. Why

389. we

390. Don’t

391. Only

392. Use

393. Fragments

394. How

395. Fragments

396. Work
•http://blog.saltfactory.net/190

397. Try

398. the

399. fragment

400. manager

401. Fragments

402. with

403. No

404. UI

405. Sunshine

406. Resource

407. Folders
•http://developer.android.com/guide/practices/screens_support.html#ConfigurationExamples

408. smallest

409. width

410. Qualifier

411. Next

412. Time…⋯
•Fragment

413. coding

414.
•CustomView