Are you an expert in Wearables technology development and design? Do you have solid teaching experience and credentials?
Wearables DevCon is for the Designers, Builders and Developers for Wearable computing devices and the applications that power them. Job titles may vary, but the attendees of Wearables DevCon will be relying on you to help get them up to speed – or increase their expertise – that will empower them to get the edge they need in this upcoming Wearables revolution.
What do these professionals all have in common? They’ll be attending Wearables DevCon in Burlingame, Ca., just minutes from the San Francisco International Airport, March 5 – 7, 2014, to learn how to master Wearable technology and devices.
Wearables DevCon kicks off on Wednesday morning with deep-dive 2-hour tutorials. Thursday and Friday contain dozens of 60-minute classes.
When you propose a tutorial or a class, be clear about the objective. Details matter. Expect to teach to your session description. For example, if you say that your session is advanced, it must be advanced. If you say your session is hands-on, it must be hands-on. We also only accept sessions that are 100% tool and vendor agnostic. Do not send a sales or marketing pitch.
|No parachuting. We want you to fully engaged in the show.
|Get your agreement and other conference materials in on time.
|Get your slides and other class and tutorial materials in by the deadline you have been given.
|Do not pitch a product, service or book during your class or tutorial.
|Start your class or tutorial on time and end on time.
|Test your AV beforehand to ensure it will work. Also have a contingency plan in the event things don’t work on site.
|Make sure you can work offline in case there is a problem with the classroom wireless network.
|Double-check that what you are teaching covers everything promised in your session title and abstract.
|Talk up the conference and your participation via Twitter, your blog, and your professional network.
|Share ideas to help make the conference content better, and recommend other excellent speakers.
|Recommend other excellent speakers from your peers and your colleagues.
In your session proposal, please tell us:
- The proposed title of your session. We reserve the right to change it to our style.
- A session description of at least 150 words, and we prefer 300 words. The more detail, you provide, the better for everyone. We reserve the right to change it to our style.
- If you will be showing code, please let us know: We highlight that in the course catalog.
- If your session is a lecture format, or if it’s a hands-on with attendees following along on their laptops.
- If you commit to providing your presentation and/or handouts at least a week before Wearables DevCon.
- Tell us if your session is Overview, Intermediate or Advanced. If you are unsure, please see our guide for session levels below.
- Explain what prerequisite skills or knowledge should be expected. Be specific!
- The speaker submission should be submitted to Wearables DevCon by the speaker himself/herself. Please also include the following information in the speaker proposal. Incomplete submissions may not be accepted.
- Your bio, 125–150 words, with a summary of your teaching expertise. We reserve the right to change it to our style.
- Your name, mailing and e-mail addresses, telephone and cell phone numbers.
- Your hi-res digital headshot, see http://www.bzmedia.com/photo.htm.
- Twitter and blog addresses (if you have them).
Please note, acceptance of your class proposal will be based not only on your topic’s timeliness and relevance, but also on your personal credentials as an Wearables expert and experience as an instructor. Be sure to communicate clearly what your class will be about, who will benefit from taking it, any prerequisite knowledge, and what the student will learn. A muddled, confused submission is likely to get rejected.
The ideal instructor is someone with real-world experience designing, engineering or developing for Wearable technology. You should have proven experience teaching practical solutions to real-world challenges, presenting new skills, and offering students an information-packed learning experience. If that describes you, please submit a session proposal electronically as a text e-mail or as a Word document to Katie Serignese, Conference Program Manager.
|• Software engineers
• Android developers
• Design engineers
• Software developers
• Project managers
• Hardware designers
• UI designers
|• Design architects
• Embedded developers
• Software architects
• App developers
• Product managers
• System architects
Conference Program Manager
Monday, December 9, 2013: Abstract submissions,
including all information described below.
Monday, December 16, 2013: Speaker notification of acceptance.
Wednesday, March 5, 2014: Tutorials
Thursday, March 6, 2014: Technical Classes
Friday, March 7, 2014: Technical Classes
Session Levels Guide
Classes and tutorials at Wearables DevCon are taught at three levels: Overview, Intermediate and Advanced.
Attendees rarely complain that a session has too much detail – but they will be disappointed if your content is fluffy. Don’t forget: This is a technical conference, and attendees want to know the details. For all development-oriented sessions, attendees expect to see code.
Overview: No previous knowledge of the class’s subject is required, and the session will be a high-level introduction of the topic. (Note: We accept very few overview-level classes.)
Intermediate: These broad technology sessions emphasize capabilities and how things work. As appropriate, the instructor will show examples or code. (Note: We accept very few intermediate classes. We suggest you take the session to a deeper level and make the class advanced.)
Advanced: These sessions teach attendees how to design and implement a solution. As appropriate, the instructor will include detailed samples or code. (We plan for at least two-thirds of sessions to be at the advanced level.)
|• Designing Postage-Stamp-Sized User Interfaces
• When Microwatts Are Precious: Battery Tips for Wearables
• Distribution Options for Wearable Apps
• Coping With Sporadic Connectivity
• Mastering the Fitbit API
• Security and Wearables
• Bridging the Digital to the Physical with Bluetooth Technology
• Android Custom Views, the Right Way
• Flashing Alternative Firmware to Sony’s SmartWatch
• Deep dive: Google’s Mirror API
• Designing Accessible Android Applications
• Adding Near Field Communication to your Wearable Device
• Understanding the UI Guidelines for Google Glass
• Mastering the Android Touch System
• Sensors, Location and Context-Awareness in Android
|• Reducing Tactile Feedback Latency in Touchscreen Applications
• Understanding and developing for the PebbleKit SmartWatch SDK
• Android Performance Tips
• Integrating Haptics into Your Wearable
• Authorizing requests to the Google Mirror API
• Exploring Android SDK Add-ons for Devices
• A Guide to Jawbone’s Up Developer Platform
• Reduce your Wearable’s Battery Usage with Bluetooth 4.0
• Getting the Most Out of the Google Mirror API Playground
• Incorporating Vibrotactile feedback into Android Apps
• Building the next generation fitness apps with the Nike+ API
• Exploring Embedded with Arduino
• Working with Timeline Cards in Building Google Glass Applications
• Syncing Your Wearable and Smartphone with Bluetooth
• FractionView: Hands-on Android Custom View Tutorial for tiny screens