Android Wear workshop Roma DevFest 2014

Nov 17, 2014Download as PPTX, PDF0 likes906 views

The document discusses a presentation given at the Roma DevFest 2014 conference about developing applications for Android Wear. It provides design principles for Android Wear apps, such as being glanceable and providing context-appropriate information. The presentation includes examples of card-based UIs and how to build a music player app that syncs notifications and playback controls between a mobile and wearable device.

No more
pocket watches
Android Wear
Antonino Orlando
Giuseppe Cerratti
e il Team del GDG Roma L-Ab

Roma
DevFest 2014
Antonino Orlando
orlando.antonino@gmail.com
it.linkedin.com/in/orlandoantonino
plus.google.com/+AntoninoOrlando
Giuseppe Cerratti
giuseppe.ciuffo@gmail.com
it.linkedin.com/in/giuseppecerratti
plus.google.com/+GiuseppeCerratti

Roma
DevFest 2014
Android Wear
developer.android.com/wear

How many time
do you spend
��lost in phone��?

Roma
DevFest 2014
Inspired by Timothy Jordan

��Android wearables provide just the right
information at just the right time, allowing you
to be connected to the virtual world and
present in the real world.��
android.com/wear

Roma
DevFest 2014
UX
Inspired by Timothy Jordan

Roma
DevFest 2014
UX
developer.android.com

Roma
DevFest 2014
Great Card
Design
developer.android.com

GDG Chat
Antonino:
See...
Roma
DevFest 2014
Card
Design
Antonino
See you later!

Roma
DevFest 2014
Time required
for each action
is 5 second

Roma
DevFest 2014
youtube.com/watch?v=sCwILO-AtEs

Roma
DevFest 2014
developer.android.com/training/wearables/
apps/packaging.html
Mobile
App
Wearabl
e
App
Distribute

Manifest.xml
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
package="it.gdglab.weare.wearaudioplayer">
Roma
DevFest 2014

build.gradle (mobile)
dependencies {
wearApp project(':wear')
compile 'com.google.android.gms:play-services:+'
}
Roma
DevFest 2014

MusicServiceClient.java
import android.support.v4.app.NotificationCompat;
import android.support.v4.app.NotificationManagerCompat;
Roma
DevFest 2014

MusicServiceClient.java
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
this.createNotify();
}
Roma
DevFest 2014

$createNotify() public void createNotify(){ int notificationId = 001; NotificationCompat.Builder notifBuilder = new NotificationCompat.Builder(getApplicationContext()); notifBuilder.setSmallIcon(R.drawable.ic_launcher); notifBuilder.setContentTitle("WearMusicPlayer"); notifBuilder.setContentText("It is time to listen"); Roma DevFest 2014$

notifBuilder.addAction(
R.drawable.ic_start, "Start", createIntent("start",
notificationId));
notifBuilder.addAction(
R.drawable.ic_stop, "Stop", createIntent("stop",
notificationId));
NotificationManagerCompat notificationManager =
NotificationManagerCompat.from(getApplicationContext());
notificationManager.notify(notificationId, notifBuilder.build());
}
Roma
DevFest 2014
createNotify()

public PendingIntent createIntent(String extra, int notifId){
Intent intent = null;
switch (extra) {
case "start":
intent = new Intent("play")
.setClass(getBaseContext(), NotificationReceiver.class);
break;
Roma
DevFest 2014
MusicServiceClient.java

��
default:
break;
}
PendingIntent pending =
PendingIntent.getBroadcast(getBaseContext(), notifId, intent, 0);
return pending;
}
Roma
DevFest 2014
MusicServiceClient.java

public void onReceive(Context context, Intent intent) {
String action = intent.getAction();
// Intent used for starting the MusicService
final Intent musicServiceIntent = new Intent(context,
MusicService.class);
musicServiceIntent.putExtra("command", action);
context.startService(musicServiceIntent);
}
Roma
DevFest 2014
NotificationReceiver.java

- The contents page uses one main image of a woman dancing surrounded by blurred men in the background, showing the spirit of dance music. - Headlines are straightforward and to the point to inform readers without needing to read the full articles. - The layout is clean cut and sophisticated with clearly separated sections. The large central image and simple text appeals to the target audience of young men interested in dance music culture.

Kartkunskapsomona

Front cover analysis (2)jgamble14

The document analyzes and compares the covers of multiple music magazines. It notes that most covers use black, white and red as core colors. It also discusses similarities in photo angles and studio shots. The target audiences vary by genre but include dance, rock, and indie music fans. Layouts and amount of text differ by magazine as well. "Mix Mag" is described as more sophisticated than others that appear more cluttered.

Front cover analysis (2)jgamble14

This document analyzes and compares the covers of multiple music magazines. It notes similarities and differences between the covers in terms of color schemes, target audiences, and layouts. The magazines share a common use of black, white, and red colors. Their target audiences vary from dance to rock music fans. The covers differ in their positioning of text, amount of text used, and level of clutter. The document also analyzes individual magazine covers like Mix Mag, Q, and Billboard in more detail, noting design elements, models, and how they appeal to intended readers.

Contents page analysisjgamble14

The document analyzes the contents pages of three music magazines - Billboard, Q, and Mixmag. For Billboard, it notes the diverse images used and simple layout with blue and black color scheme. For Q, it highlights the overlapping on-location artist photos and minimal text. For Mixmag, it describes the single glittery image of a dancing woman, straightforward article titles, and clean layout with image taking up most space.

Front cover analysis (2)jgamble14

This document analyzes and compares the covers of multiple music magazines. It notes similarities and differences between the covers in terms of color schemes, target audiences, and layouts. The magazines share some common colors like black, white, and red. They also take splash photos in a studio at a medium-long shot angle. The target audiences vary between genres like dance, rock, and indie. Differences include the amount of text, positioning of elements, and level of clutter. The document examines individual magazine covers in more depth, analyzing aspects like colors, images, fonts, and how well the covers appeal to their intended readerships.

Jeffrey m adams professional research and student work v2Jeffrey Adams

This document provides examples of professional work and student work by Jeffrey M. Adams. The professional work section lists 18 sculptures Adams has created with various materials like cast bronze, steel, wood, and fabric. The student work section displays assignments and thesis work Adams has done with his students utilizing materials such as plaster, resin, clay, and found objects to explore themes of self-reflection, American culture and current events.

Media evaluation q1jgamble14

The student discusses how their media product both uses conventions of real music magazines as well as challenges some conventions. For the front cover, conventions like eye contact in photos and a large central image were used, but a black and white "underground" photo challenged typical studio shots. Minimal text on the cover follows conventions but risks not providing enough information. The contents page layout draws from Billboard but challenges Q magazine's convention of many photos over text. Across pages, different shades of blue are used to tie the magazine together visually, challenging the convention of varied colors between articles.

Special Edition: Apple and/vs Google [Infusion - 11th July 2014]AlquimiaWRG

Developing Android Apps for Google AssistantKenichi Kambara

This document discusses developing Android apps for Google Assistant. It explains that there are two main approaches: using the Google Assistant for Android or developing original Android apps. For original apps, it covers client-server communication between Dialogflow and an Android app using requests and responses, as well as creating the app's user interface. Code examples in Kotlin are provided to illustrate setting up communication with Dialogflow from an Android app.

Teaching Your Client Android Design, or, Don't Be An iPhoneyKenton Price

This document discusses teaching clients proper Android design by avoiding direct ports from iOS ("iPhoney") apps. It emphasizes that Android apps should be designed specifically for Android, following Material Design guidelines and principles like responsive design. The document outlines issues with pixel-perfect designs across devices and provides case studies of successfully transitioning apps like The Sun Mobile and BBC Weather from iOS to high-quality Android apps by adding recommended Android features and patterns.

�ձ�android�λᶨ��2016��6��_Android Wear 2.0��v�Bչʾ�B��Kenichi Kambara

This document discusses Android Wear 2.0 which was announced at Google I/O 2016. It provides an overview of sessions, exhibitions and code labs about Android Wear at I/O 2016. It also compares the features and APIs of Android Wear 1.x and 2.0, noting new additions in 2.0 like the Wear Input Method Framework and improved Material Design. Finally, it lists the speaker's social media profiles and emphasizes their work with Android Wear.

Remarkable Matters: Remarkable Mobile DesignTable19

Droidcon Italy 2020 report Francesco Ronchi

14 Web tech trends 2014Fr?jd Interactive

In this report, Fro?jd Interactive - a web agency with technical core located in Stockholm, Sweden - sums up what to expect of 2014. As always, the future is already here. So, we have focused on 14 things that we believe will hit it big & mainstream in Sweden next year. Which means - if you haven��t started developing things in the direction of this presentation �C you better start now. Enjoy!

Doaa-VR-lecture1.pdfDoaa Mohey Eldin

Virtual Reality and Augmented Reality are emerging technologies that were discussed. VR uses headsets to create immersive 3D experiences by simulating reality, while AR enhances the real world with digital information. Their applications include education, training, healthcare, gaming, and more. Key differences are that VR completely immerses users in virtual environments and requires headsets, while AR blends virtual and real-world elements seamlessly. Both saw rapid growth and are important for industries like data science due to their ability to enhance analytics and decision making through machine learning.

Android Training Course In ChandigarhExcellence Academy

Seizing the Mixed Reality Revolution �C A past, present and future Mixed Reali...Windows Developer

The document discusses top development recommendations for building applications for the HoloLens and other mixed reality platforms. The top recommendation is to learn about deep learning. Other recommendations include treating the HoloLens like a mobile device, offloading processing when possible, designing in 3D, anchoring holograms in the real world, leveraging the mixed reality community, and building for the entire mixed reality platform. Links are provided for additional learning resources.

Building for Google AssistantRalph Vincent Regalado

The document discusses building actions for Google Assistant. It provides statistics on voice search usage and outlines the different types of actions like direct actions and conversation actions. It then gives steps to create a conversation action using API.AI and deploying it, including creating a Cloud Project, registering the conversation, and interacting with it. References for further information are also provided.

Coders4Africa Ethiopia Developers & Technopreneurs Conference 2014: Building ...John Adams

The Publisher's Response, Digiday WTF VR, May 11th, 2016Digiday

This document discusses key considerations for creating cross-platform virtual reality (VR) content, including supported devices, distribution options, and content types. The main VR headsets - HTC Vive, Oculus Rift, Gear VR, and Cardboard - vary in quality, cost, and functionality. Distribution can occur via platforms like YouTube and Facebook, as well as native apps. Content is commonly computer generated 3D environments or 360-degree video. A case study highlights an interactive VR installation versus a higher quality but non-interactive public release.

Android Training in Chandigarh.pdfExcellenceTechnology9

Storytelling using Immersive TechnologiesKumar Ahir

This is Kickstarter presentation for understanding the domain of Immersive technologies and giving a guide to creating an immersive experience using Unity, Vuforia and Aframe. Even before we get into how to do StoryTelling using this new media, we need to understand what's possible and where is it heading, which positions us better to design the story and capture it properly. This help you understand the ecosystem of Immersive Technologies from Business, Product, Design and Development perspective.

Thibaut rouffineauapps4allru

This document appears to be from a conference on mobile apps and contains summaries of 8 conversations that took place. The conversations discuss topics such as apps versus HTML5, wearables, developer teams, monetization strategies, the size of the mobile app market, exits and acquisitions, and being a successful entrepreneur. Tables and charts are included that provide statistics on app downloads and revenue from app stores.

Google IO - Five months laterMatteo Bonifazi

Designing an App: From Idea to MarketEffectiveUI

Designing an Android App: From Idea to MarketEffective

Android Wear workshop Roma DevFest 2014

1. Roma 2014 Google DevFest

2. No more pocket watches Android Wear Antonino Orlando Giuseppe Cerratti e il Team del GDG Roma L-Ab

3. Roma DevFest 2014 Antonino Orlando orlando.antonino@gmail.com it.linkedin.com/in/orlandoantonino plus.google.com/+AntoninoOrlando Giuseppe Cerratti giuseppe.ciuffo@gmail.com it.linkedin.com/in/giuseppecerratti plus.google.com/+GiuseppeCerratti

4. Roma DevFest 2014 Android Wear developer.android.com/wear

5. ��Be glanceable��

6. Ever had a date?! Roma DevFest 2014

7. Ring Riiing!!! Roma DevFest 2014

8. Roma DevFest 2014

9. Roma DevFest 2014

10. How many time do you spend ��lost in phone��?

11. Roma DevFest 2014 Inspired by Timothy Jordan

12. ��Android wearables provide just the right information at just the right time, allowing you to be connected to the virtual world and present in the real world.�� android.com/wear

13. Design Principales

14. Context stream first!

15. Roma DevFest 2014 UX Inspired by Timothy Jordan

16. Roma DevFest 2014 UX developer.android.com

17. Card!

18. Roma DevFest 2014 Great Card Design developer.android.com

19. GDG Chat Antonino: See... Roma DevFest 2014 Card Design Antonino See you later!

20. Gone in five seconds!

21. Roma DevFest 2014 Time required for each action is 5 second

22. Leave Kimi alone!

23. Roma DevFest 2014 youtube.com/watch?v=sCwILO-AtEs

24. Debug

25. Distribution

26. Roma DevFest 2014 developer.android.com/training/wearables/ apps/packaging.html Mobile App Wearabl e App Distribute

27. Manifest.xml <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="it.gdglab.weare.wearaudioplayer"> Roma DevFest 2014

28. build.gradle (mobile) dependencies { wearApp project(':wear') compile 'com.google.android.gms:play-services:+' } Roma DevFest 2014

29. Roma DevFest 2014 Distribute

30. {Let��s Code!}

31. Synced Notification Roma DevFest 2014

32. MusicServiceClient.java import android.support.v4.app.NotificationCompat; import android.support.v4.app.NotificationManagerCompat; Roma DevFest 2014

33. MusicServiceClient.java @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); this.createNotify(); } Roma DevFest 2014

34. createNotify() public void createNotify(){ int notificationId = 001; NotificationCompat.Builder notifBuilder = new NotificationCompat.Builder(getApplicationContext()); notifBuilder.setSmallIcon(R.drawable.ic_launcher); notifBuilder.setContentTitle("WearMusicPlayer"); notifBuilder.setContentText("It is time to listen"); Roma DevFest 2014

35. notifBuilder.addAction( R.drawable.ic_start, "Start", createIntent("start", notificationId)); notifBuilder.addAction( R.drawable.ic_stop, "Stop", createIntent("stop", notificationId)); NotificationManagerCompat notificationManager = NotificationManagerCompat.from(getApplicationContext()); notificationManager.notify(notificationId, notifBuilder.build()); } Roma DevFest 2014 createNotify()

36. public PendingIntent createIntent(String extra, int notifId){ Intent intent = null; switch (extra) { case "start": intent = new Intent("play") .setClass(getBaseContext(), NotificationReceiver.class); break; Roma DevFest 2014 MusicServiceClient.java

37. �� default: break; } PendingIntent pending = PendingIntent.getBroadcast(getBaseContext(), notifId, intent, 0); return pending; } Roma DevFest 2014 MusicServiceClient.java

38. public void onReceive(Context context, Intent intent) { String action = intent.getAction(); // Intent used for starting the MusicService final Intent musicServiceIntent = new Intent(context, MusicService.class); musicServiceIntent.putExtra("command", action); context.startService(musicServiceIntent); } Roma DevFest 2014 NotificationReceiver.java

�ݺ�ߣ

Android Wear workshop Roma DevFest 2014

Recommended

More Related Content

Similar to Android Wear workshop Roma DevFest 2014 (20)

Android Wear workshop Roma DevFest 2014