[conference] KR Mobile Week 2013

Title	KR Mobile Week 2013
Place	COEX Grand Ballroom 101
Time	July 15, 2013 10AM~5PM
Speaker	Chris Yerga, Dan Galpin, Haisoo Shin and more
Organizer	Google Korea
Focus	Android, Google+, YouTube API

I.       Welcome & Keynote [yerga@; Chris Yerga, Engineering Director]

II.      Android Platform Updates [dgalpin@; Dan Galpin, Developer Advocate for the Android team]

1.       Updates

1)      Google Play service updates

①  Google Maps Android API v2

②  Location APIs

A       Fused Location Provider- more accurate result

B       Geofencing- (A geo-fence is a virtual perimeter for a real-world geographic area. <source: Wikipedia>)

C       Activity Recognition- help users measure physical activity

③  Google+ Sign-In

④  Google Cloud Messaging (GCM)- synced messaging

A       GCM (Definition: a service that helps developers send data from servers to their Android applications on Android devices, or from servers to their Chrome apps and extensions. <source: Wikipedia>)

2)      Google Play game services updates

①  Cloud save

②  Achievements- share achievement w/ friends

③  Leaderboards- how much better you are compared to friends

④  Multiplayer- through mashed network

3)      updated Android Studio, NDK

2.       What’s next?- Faster UI, reordering & merging, multi-threading, Bluetooth LE (low energy), Android on TV (Latest Chrome, Project Butter, NDK)

III.     YouTube API Platform Updates [amandas@; Amanda]

1.       Updates

1)      YouTube- is a platform that can empower the next generation of video-based businesses

①  Tastemade (food network)

2)      YouTube API

①  Creation

②  Disocvery + context

A       Topics API- e.g. intersante (recommendation), Soundslice

③  Live streaming- e.g. elgato

④  BuzzFeed

⑤  Enterprise- E.g. mediastudio

⑥  Analyticis + promotion- audience analytics (e.g. tubular’s awesomenesstv), trend meter (e.g. Next Big Sound; for artists how to improve their marketing)

IV.     Google+ Platform Updates [cartland@; Chris Cartland, Developer Programs Engineer]

1.       Updates

1)      Google+ benefit: one identity (one google account) relationships (circles),  sharing and recommendations (share w/ the right people)

2)      Social Sign-in Examples

①  The Guardian- user choices (facebook, g+, twitter, etc)-> user control

②  Snapette- increased user registration by 16%

③  Fandango- app installs-, 40% acceptance rate for over-the-air installs

④  Fancy- cross-platform single signon

⑤  OpenTable- explicit sharing (interactive post), deep linking

⑥  Glamour- YouTube integration

⑦  Forbes- content recommendations

⑧  Flixster- Google Calendar integration

V.      Google+ Sign-In partner Fancy.com talk [Haisoo Shin, Director of Engineering at Fancy]- G+ Sign-In

1.       Fancy service intro

1)      Fancy- means like

2)      USP- includes purchase function

2.       Key takeaways

1)      Barrier examples for users- discovery, app installation, sign-up, payment

2)      An example to lower registration barrier- Google+ Sign In

3)      Examples to enhance installation and discovery function- app installs, interactive posts, cross-platform SSO, etc.

VI.    Play Services API (Location / GCM) [htchan@; Tony Chan, Android Developer Advocate]

1.       Updates (for Google I/O video: bit.ly/io13-android)

1)      Notification

①  Cloud Connection Server (CCS), Upstream Message, User Notifications, etc.

②  CCS vs. GCM

2)      Location APIs- using sensors like gyro, barometer, accelerometer, GPS

①  High accuracy- 10 meters, 5 sec

②  balanced power- 40 meters, 20 sec

③  no power- 1 mile, N/A

3)      activity recognition- vehicle, on foot, still, on bicycle

4)      Geofencing

2.       Key takeaway

1)      How to combine two Geofenching & GCM: e.g. promotion in a geofence

VII.   Supercharge your Apps with the YouTube API Platform [jarekw@; Jarek Wiliewicz, Developer Advcate]

1.       Updates (4 kinds)

1)      Creators- Creation e.g. elgato, everyplay,

2)      Viewers

3)      Enterprises

4)      Marketers

2.       Reference: youtube.com/dev

VIII.  Modern Android Design [pakoch@; Adam Koch, Android Developer Advocate]

1.       Updates

1)      Design patterns: navigation, navigation drawer, unofficial patterns

①  Action bar: consistent bar (component: brand/app icon, drop-down spinnup, search, movie), Action Overflow (extra options)

②  Navigation: spinner (drop-down navigation item), fixed tabs (underneath action bar), scrollable tabs, drawer (primarily for main app navigation, Action Bar stays in place, Drawer overlays content)

③  Navigation Drawer Interaction: introduce the drawer on first use, give the user a quick peek, highlight the current screen)

④  Unofficial patterns: Fading Action Bar (introduced in Google Play Music, part of other Play apps as well), Swipe to Refresh (experimental pattern, currently only used by Gmail app), Action Drawer (used by Google+, One Today for app notifications, shows scrollable list of items), Cards

2)      Responsive design: why responsive?, SlidingPanelLayout, Other tips

①  Device variety- screen size, resolution, vertical to horizontal support

②  Why responsive? – android:layout_width=”match_parent”

③  Combination- side-by-side

④  Fragments

⑤  Master/Detail Flow template-> File > New> Android Object

⑥  SlideingPaneLayout- enough room then show everything, if no, then slides to the right (e.g. Google I/O 2013 app)

⑦  Dimension files- page_margin, headline_text_size, etc)

3)      Pure Android: Why Android/Holo?, Balancing Brand andPlatform Consistency

①  Why design Android/Holo?

A       Better User Experience- Platform consistency, intuitive use of app, improved usability, engaging content-first design)

B       Easier, More Robust Technical Implementation- designed to handle hardware variations such as screen sized, densities, on-screen vs. hard navigation buttons, OS version and device compatibility)

C       Beautiful, Flexible Design- efficient use of white space and typography

D       Brand consistency- split into IA, IxD, Visual design

4)      Examples- Fancy (card base, scale on a different sizes), Expedia (split screen into 2 for tablet), TED (action bar, thumbnails)

2.       Reference

1)      Google I/O 2013: Google.com/io

2)      Android Design in Action: androidDesignInAction.com

3)      Android Design Site: developer.android.com/design

4)      Navigation Drawer: developer.android.com/design/patterns

5)      Responsive Design: Goo.gl/RY1dT

6)      Other resources: goo.gl/hh8pg

IX.     How to build a great Android app [khmin@;Kyunghwan Min, Korea Lead, Apps & Games Google Play]

1.       Key takeaways

1)      ABC of Building Application

①  all screen size adaptable

②  Android design guidelines (esp. Action Bar, Navigation, Pure Android)

A       #1: Action Bar- delete unnecessary items

B       #2: Navigation (Up vs. Back)- in game, back button-> pause

C       #3: Pure Android- use Google identity icons (e.g. no text included icon, no right arrow, use API)

③  Quality Checklist

④  Localized screenshot, video, etc

2)      ABC of Marketing Application

①  Create an awesome Play store listing

A       Feature Graphic- need a promotion banner (device image, screenshot)

B       Description, Title- use user query, be careful in using promotional description

C       Icon- use unique representative icon

②  Simplify Sign-in w/ G+- drive downloads/ increase engagement

③  Increase downloads through Play badging- e.g. Get it On Google play

④  Immediate Play- get ready for users to start playing games right away (include GUEST LOGIN icon)

2.       Reference

1)      developer.android.com/distribute

2)      play.google.com/+

X.      New words

1.       Schema: In psychology and cognitive science, a schema (plural schemata or schemas), describes an organized pattern of thought or behavior. It can also be described as a mental structure of preconceived ideas, a framework representing some aspect of the world, or a system of organizing and perceiving new information. <source: Wikipedia>

2.       URI: In computing, a uniform resource identifier is a string of characters used to identify a name or a web resource <source: Wikipedia> c.f. http://goo.gl/4XGVDv

3.       JSON: or JavaScript Object Notation, is a text-based open standard designed for human-readable data interchange. It is derived from the JavaScript scripting language for representing simple data structures and associative arrays, called objects. Despite its relationship to JavaScript, it is language-independent, with parsers available for many languages. <source: Wikipedia>

4.       Geo-fence: A geo-fence is a virtual perimeter for a real-world geographic area. <source: Wikipedia>

5.       Taxonomy: is the process of naming and classifying things such animals and plants into groups within a larger system, according to their similarities and differences <source: Collins Cobuild>

6.       Google Cloud Messaging (GCM)- is a service that allows you to send data from your server to your users' Android-powered device, and also to receive messages from devices on the same connection. The GCM service handles all aspects of queuing of messages and delivery to the target Android application running on the target device. GCM is completely free no matter how big your messaging needs are, and there are no quotas. <source: developer.android.com>

7.       Alan Kay- Alan Curtis Kay (born 17 May 1940) is an American computer scientist known for his early pioneering work on object-oriented programming and windowing graphical user interface design. <source: Wikipedia> 

[conference] Google Developers Summit 2014

Title	Google Developers Summit 2014
Place	COEX Grand Ballroom 104, 105
Time	February 26, 2014 1PM~6:30PM
Speaker	Ryosuke Matsuuchi, Mickey Kim, et al.
Organizer	Google Korea
Focus	Android design guideline, Chromecast API, Google Play utilization

I.       Android design guideline [Chansuk Yang, Developer Relations]

1.       Message

1)      Basic advice

①  targetSDK>19 (meaning use the most recent)

②  change support package level to support minimum Android OS level

2)      What’s new in KitKat

①  Home menu button: use app launcher icon as home menu button

②  Visual design: when design, comply with people’s mental model so users don’t need to learn something new

③  Two gestures: for zooming in and out, double touch or double touch drag

④  Full screen mode: lean back mode (touching the screen in any way will bring navigation and notification bar back into place.), immersive mode (swiping down from the top or up from the bottom will bring notification bar or navigation bar respectively)

3)      Android design pattern

①  Action Bar: app icon, view control, action buttons, action overflow

A       Suggestion: Android doesn’t recommend customized Action Bar

②  Up and back difference

A       Up: higher category

B       Back: previous page or closing a pop-up window

③  App structure

A       Tab: fixed and scrollable tabs; needs to be located at the top of the screen; needs to support swiping

B       Navigation Drawer: system bar needs to stay

④  Dialogue and Toast principle

A       Principle

l  How much impact will the action bring to users? E.g. purchase brings a great impact

l  Does it allow users miss-click?

l  Can the result of the action returnable?

l  Sufficient user feedback to users? E.g. Facebook’s like button

B       Example: closing an app-> taking too much time-> consider using Dialogue window

⑤  Notification: utilize expand and contract option

4)      Responsive design

①  Need to support tablet

②  Use DP (density-independent pixels) (e.g. 200 dp)

③  Resource qualifier- provide different size icons

2.       Takeaway

1)      targetSDK>19 (meaning use the most recent)

2)      Home menu button: use app launcher icon as home menu button

II.      Chrome WebView Essentials [Alex Danilo, Developer Advocate]

1.       Message

1)      What does this mean?

①  New capabilities:

A       indexedDB: important technology to store data (e.g. games)

B       Web Sockets: push data back and forth client and server

C       requestAnimationFrame: synchronize animation on screen (not wasting time compared to JavaScript)

D       SVG filters and Effecs: e.g. convolution blurs

E       H/W accelerated rendering (e.g. <canvas>)

②  Debugging Features: Analyzing web traffic, monetizing

③  Hybrid applications: Use native component, interfacing JavaScript to native

④  Compatibility mode: Use targetSDK>19

⑤  Multi-threading and thread blocking

⑥  Custom URL Handling: URLs must conform to RFC 3986

⑦  Viewport Changes

⑧  Styling Changes

⑨  Sizes are in CSS pixels instead of screen pixels

2)     Best practices

①  Set SDK version to 19: <uses-sdk android:targetSdkVersion=”19”.>

②  Enable hardware acceleration: <application android:hardwareAccelerated=”true” ..>

③  Enable Debugging: WebView.setWebContentsDebuggingEnabled(true);

3)      The Future: Web RTC (real-time communication; P2P communication; e.g. Google Hangouts is coming

2.       Resources

1)      documentation: http://goog.gl/1gJ8gp, http://goog.gl/Xj2zpK

2)      samples: http://goo.gl/2LfCBS

3)      twitter: @alexanderdanilo; g+ google.com/+alexdanilo

III.     New AdMob- profitability, convenience and control [Siyoung Choi, PBS AdMob Lead]

1.       Message

1)      Best practice

①  Why it got popular:

A       YouTube video review (subscription 3 M)

B       Review: ## reviews

C       Community BBS

D       Siyoung’s insight: Low requirement, short game time, free

②  Ways to purchase mobile app contents: Freemium, in-app purchase, download

③  수익= 매출 - 비용

A       운영서버, 퍼블리싱, 분석도구, 마케팅채널, 보안솔루션, 결제솔루션

B       매출: DL x재방문율x결제율x ARPPU

C       매출 결정 변수: 마케팅x In app 설계x service balance x결제지원수단, 개인별 결제 한도

④  모바일 광고: 사용자는 돈을 내지 않고 광고주가 대신 지불+손쉬운 적용, 안정적 수익, 적은 투자

2)      AdMob 특장점

①  Reach and scale: Google Play global target, localization languages

②  Innovative ads: 전면 동영상 등 creative

③  High fill-rate: traffic이 수익화에 적용

3)      광고 수익의 규모는

①  계산: 10M user, 노출율 90%, CPC 100 KRW, xxx -> 9M KRW

4)      New AdMob

①  편의성: 빨라진 지급주기, 앱 개발자에게 최적화 된 UI (수익화/홍보 지원), 앱 업데이트 없이 mediation, house ad 적용

②  수익성: 전환최적화 기능 (자동으로 단가 최적화), 수익 극대화 (mediation 활용- Optimize AdMob Network)

③  컨트롤: 세분화된 필터링 (140여개 예. 경쟁사 광고 제외), 광고 심사 센터

5)      광고 수익화를 위한 적용 Tip  

①  Refresh rate: 30~60 seconds

②  광고와 컨텐츠의 경계

③  Smart banner 사용: portrait <-> landscape

④  전면광고: 사용자 별로 노출횟수 조절, 사용자가 즐거울 때, user flow 끊기는 지점, 호출과 노출분리, 최신 SDK 사용, Google Analytics 사용

2.       Takeaway

1)      Request to convert to New AdMob at Bit.ly/newadmob

2)      광고 수익화를 위한 적용 Tip

①  Refresh rate: 30~60 seconds

②  광고와 컨텐츠의 경계할 것

③  Smart banner 사용: portrait <-> landscape

④  전면광고: 사용자 별로 노출횟수 조절, 사용자가 즐거울 때, user flow 끊기는 지점, 호출과 노출분리, 최신 SDK 사용, Google Analytics 사용

IV.    Chromecast [Mickey Kim, Head of Asia Pacific, Chromecast]

1.       Message

1)      Lesson Google learned

①  need setup experience to be easy

②  need nothing new to learn

③  need to support cross platforms and devices

④  need to support second screen (smartphone, tablet, laptop)- because 77% of the time while watching a TV, second screen has been used; the bigger the screen, the more YouTube people watch

2)      setup process: plug in-> connect to Wi-Fi-> cast (bringing optimized resolution depending on screen size)

3)      benefit

①  video and audio cast to TV

②  Chrome web browser tab mirroring

2.       Takeaway

1)      Just add code from Cast SDK at developer.google.com/chromecast into your smartphone, tablet and website

2)      Review the Cast UX requirements and integrate

V.      Google Cast SDK Overview [Chansuk Yang, Developer Relations]

1.       Message

1)      Download SDK at developer.google.com/cast

2)      Google Cast 구성요소

①  Sender Application:

②  Receiver Application:

③  Cast Device

④  Streamiing media server

3)      Check out

①  User Experience with Google Cast at https://developers.google.com/ast/docs/ux_guidelines

②  Google Cast Design Checklist:

4)      Google Cast SDK 구성요소

①  Sender SDK- Android (google Play Service), iOS (SDK), Chrome (JavaScript)

②  Receiver SDK- Receiver Library & Media Player Library (JavaScript)

③  Cast Developer Console

5)      시작하기

①  Google Cast Developer Console 계정 등록- $5 onetime fee, receiver app/device registration and management

②  Receiver app 등록: Ap ID 발급

③  Cast Device 등록 (unlock)- 개발, 디버깅, 테스팅을 위해

6)      Sender Application: cast device 검색, receiver app 실행, 보안 채널 연결, UI control, media message sending, custom message sending

7)      Receiver application: 단순 웹 어플리케이션, 컨텐츠를 표시하기 위한 인터페이스 제공, 미디어 컨텐츠를 컨트롤 하기 위한 메시지 수신 및 처리, 앱에 특화된 사용자 정의 메시지 수신

8)      Receiver application 종류: default receiver, styled receiver (CSS 만 등록), custom receiver,

9)      Supported media: most open format

10)    Google Cast Sample apps: github.com/googlecast

11)    Stack Overflow: #google-cast

2.       Takeaway

1)      Include Chrome Cast in your app