[Android dev: "쉽고 재미있는 안드로이드 앱 개발"] Android class just started at Fastcampus nearby Gangnam Station

Haven't posted for a long while. :) Now I'm BACK!

Regarding Android class I am taking, will post more in detail soon but below is our syllabus and content links. 

2017.12.19.~ 2018.1.25. | 총 6주
매주 화/목요일 19:30 ~ 22:30

Android 전체예제: https://github.com/adsloader/AndroidKotlinExample

Kotlin 전체예제: https://github.com/adsloader/FirstKotlin

Kotlin 동영상 강의: https://www.youtube.com/watch?v=6CcMQW6iFEw&list=PLRMWteUGYj2WsOL8hwaN_qgM3VohfaVY3

1일차: 강의목표, install 개발툴, 핸드폰 개발자 모드, App 만들기

2일차: Project 관리와 Android Studio 사용법, 화면 디자인(XML) - 1, 화면 디자인(XML) -2

3일차: 화면 디자인 (XML) -3, Before Programming, start Kotlin - 1

4일차: start Kotlin - 2, start Kotlin - 3, 화면 디자인 (XML) - 4

5일차: Activity의 기본 - 1

6일차: Activity의 기본 - 2

7일차: Activity의 기본 - 3

8일차: 계산기와 숫자 맞추기

9일차: 보이지 않는 프로그램

10일차: 퍼미션과 웹(HTTP, WebView)

11일차: 카드만들기와 주사위 게임

12일차: FireBase 그리고 향후 공부방법

[productivity: my takeaway] after watching "Manage your time like a Google Pro | Calendar | The Apps Show"

Video: https://www.youtube.com/watch?v=RSvnq3r2bcU
post from Google Apps for Work: https://apps.google.com/learn-more/make-time.html
post from Medium: https://medium.com/@googleforwork/one-googler-s-take-on-managing-your-time-b441537ae037#.8v410ykyg

2 things I learned:
1. The Weekly Pulse - research result: "Energy starts low on Monday when you come out of the weekend and it peaks on Tuesday and Wednesday and it comes back down through the end of the week." - actionable example: on Mondays, plan week and set goals for the week; on Tuesdays and Wednesdays, make time for creative and GTD; on Thursdays, reach agreement with people (e.g., 1:1's, meetings for consensus); on Fridays, write expense reports, purchase orders, and attend compliance training 2. Description and Meeting Notes Attachment - Description: add "OWNER: (who will lead this meeting?)", "TYPE: (decision/1:1/informal catch up/etc.)", and "PURPOSE: (what's the goal or outcome? is any prep required?)" - Meeting Notes: "date of the meeting," "thoughts from the team (things attendees want to mention)", and "updates (room for updates or collaboration efforts that people are working on)"

[my note: conference] Google Developers Summit 2016

Subject	Google Developers Summit 2016
Place	Nine Tree Convention Gwanghwamun, Seoul Korea
Time	April 28, 2016 (Thu) 13:20~18:00
Speaker	link
Host	Google
Focus	mobile web and app; web (progressive Web, next Web, push Notification)

1. Intro to Progressive Web Apps (Robert Nyman, Google)
1. Lesson
1. Native & the web: “Wait! The Web Isn’t Dead After All. Google Made Sure of It”- Wired
2. From “app storage page view” to “post or send to friends,” every step costs you 20% of users- Gabor Cselle
3. RAIL: instant loading and smooth navigation
4. SLICE: build an app not requiring installation
1. Secure: be intentional when asking for user permissions
2. Linkable: provide a direct link per paragraphs
3. Indexable: make sure my contents can be found via search engines
4. Composable: how you combine things
5. Ephemeral: don’t require too much steps
5. Why needing a native app?
1. Performance, offline access, periodic background processing, notifications, sensors (GPS, Bluetooth), OS-specific features
6. Progressive web app (or PWA)
1. Reliable: fast loading, works on flaky networks
2. Fast: smooth animation, scrolling, and nav
3. Engaging and integrated: full screen with no URL bar, sending notifications even when page closed
7. Required
1. Service Worker
2. Web app manifest
3. App shell caching
8. Recommended features
1. Push notifications
2. Advanced offline support
9. PWA should work across all browsers (e.g., Chrome, Firefox, Opera)
10. Add https to your web site for security (e.g., SSL for free, Cloudflare, bit.ly/ssl-labs)
11. Usecase
1. Flipkart
1. 3x time spent on site
2. 40% visitors return week over week
3. Smooth experience on even 2G & flaky networks

2. Personal Takeaway
1. Use HTTPS
2. The term Service Worker

2. What’s new in Android N (Chansuk Yang, Google)
1. Lesson
1. Android Beta Program: google.com/android/beta (c.f., don’t run this program on a regular phone but run on a test phone)
2. N for Developers:
1. Multi-window: split view, PIP, free-fall?
2. battery optimization:doze in N-release (no network access, jobs/syncs deferred); Doze Optimization (e.g., foreground service for music streaming service)
3. datasaver, background optimization
3. N Developer Checklist
1. Check Multi window
2. CONNECTIVITY_CHANGE, NEW_PICTURE NEW_VIDEO
3. Doze
4. Datasaver mode
5. Notification template
6. Supporting various screen size and orientation
7. Background tasks such as service/broadcast receiver needing to be used only when needed
8. Repetitive task-> battery optimize
9. Be careful in allowing permissions
4. References: d.android.com/preview; developer.android.com/preview/samples

2. Personal Takeaway
1. Go through checklist to prepare for N

3. Instant and Offline Apps with Service Worker (도창욱, GDE)
1. Lesson
1. Benefit
1. Instant loading: c.f., “Amazon found every 100ms of latency cost them 1% in sales”
2. Goals
1. Compression
1. Use minification & gzip: e.g., min.js; min.css
2. WebP: smaller than JPG
1. Use <picture> tag and prioritize image formats
2. Round trips (wasteful time)
3. Be interactive: script async defer
4. CSS: https://aerotwist.com/blog/guitar-tuner/ or https://guitar-tuner.appspot.com/
5. Defer iframes
6. Http2: connection share
7. Offline:
2. Service Worker (a JavaScript module)
1. Only support https
2. Useful for 404 error page
3. Reference: https://jakearchibald.github.io/isserviceworkerready/

2. Personal Takeaway
1. SW has instant loading benefit!

4. Making it Installable (문현경Jimmy Moon, GDE)
1. Lesson
1. Installable web apps in 2 simple steps
1. Create a manifest (a json file)
1. E.g., {“name”: “The Airhorner”...}
2. Link it to your page
1. E.g., link=
2. Flow
1. User clicks “Add to home screen”
2. Confirmation prompt shown
3. ...
3. Splash screen
4. Requirement for prompt to install: offer an offline experience (i.e., Service Worker, HTTPS), hae a manifest (define what to launch and how to launch it), user …
5. Tool for icon: http://realfavicongenerator.net/

2. Personal Takeaway
1. Term splash screen
2. Prompt to install

5. Deeper Engagement with Push Notification (고재도, GDE)
1. Lesson:
1. Ask yourself: is it important to interrupt users by sending notifications?
2. Anatomy of notification
1. Timely
2. Precise
3. Relevant
4. Work offline
3. Notification example: e.g., flight delayed, credit card last purchase amount,  your self driving car has arrived, thanks for installing me
1. Subscribing users
4. C.f., Propel

2. Personal Takeaway:
1. Anatomy of notification: Timely, Precise, Relevant, Work offline

6. Putting the Progressive in Progressive Web Apps (Sam Thorogood, Google)
1. Lesson
1. Definition of Progressive Enhancement
1. What: works in every browser
2. How: incremental use of APIs
3. Why : diverse users (different device)
2. Imperative HTML
3. Push:
1. Notification: info
2. User engagement: user re-engagement for helping them buy products or consume contents
3. Ask questions:
1. What do you know about them- email, phone #, twitter, facebook
2. Why are you engaging with them- informative or actionable
3. Do you need to be timely
4. Are you already engaging with them?
4. Transport idioms
1. Native
1. Send timely and engaging notifications, no user login required
2. Email
1. Send HTML email with actional buttons
2. context/platform might be different- provide login hint (help users just to enter password instead of ID and password)
3. SMS
5. Leverage the browser: e.g., <input autocomplete=>
4. Install:
1. The modern way: e.g., <link rel=”manifest” href=”/manifest.json” />
2. Best practice: “Add to Home Screen” hint
3. Browser tab or standalone?: content (browser tab) vs. utility (standalone)
5. Offline:
1. Offline capable: if a site can be cached, then you should operate well
2. Network as a feature:
1. assume your site is always offline, unless proven otherwise
2. Every load, image fetch starts with the assu…
6. User perception
1. Loading wheel image: iOS image (people blame the OS) vs. Facebook loading image (blame the app)

2. Personal Takeaway
1. Due to user perception, use iOS loading image ^^;

7. The Future of the Web (Paul Kinlan, Google)
1. Lesson
1. Friction was removed over time
2. Distribution is the hardest problem in software
3. Engagement has been achilles’ hill on web
4. Placement of PWA: Mobile Web -> Progressive Web Apps -> App
5. The future of the web is not about APIs
1. Multi-device exp: one code for all
2. Faster exp: load instantly via Service Worker
3. HTTPS everywhere: use Service Worker
4. Engaging and reduced friction: optimize UX of push notifications (e.g., Facebook’s push notification)
6. Be fast everywhere (site load instantly)
1. Amp
2. RAIL
7. Move to HTTPS
1. Camera
2. Auto-fill
3. Push
4. Geo-location is disabled now
5. Full-screen will be disabled
8. Be engaging
1. E.g., Flipkart- conversion increase, return increase
9. Service worker is the glue that binds the future of the Web
1. Entire sites now have an app-like lifecycle.
10. ES2015: Promises, ...
11. Stream: fetch-> process-> render
12. Background Sync: defer network request until online, great for ensuring transactions happen
13. Credential Management- store credentials for re-use, get saved credentials (across devices)
14. Media Stream Recorder-
15. Web Bluetooth
16. Physical Web: user opt-in
17. Reference: https://www.chromestatus.com/features

2. Personal Takeaway
1. Vysor: controllable window of your Android on your desktop