Skip to main content

MobDevCon 2014: Call for Papers

By
Conference: Wednesday 9th July 2014
Submission Deadline: 14th February 2014 (email: mobdevcon@nakedelement.co.uk)
Where: The Kings Centre, Norwich (new venue for 2014)
Web: http://mobdevcon.com
If you would like to be kept up-to-date about MobDevCon, please join our email list here and follow MobDevCon here: @mobdevcon. 

Call for Papers & Speakers

Following the sold out success of last year’s conference, Naked Element Ltd. is proud to present MobDevCon 2014, Norfolk’s Mobile Development conference. The conference will be held on Wednesday 9th of July at The Kings Centre in Norwich, UK. Naked Element Ltd. would like to invite proposals for sessions.
The keynote speakers have already been confirmed:
Submissions should be made by the 14h February 2014 to mobdevcon@nakedelement.co.uk and include the following information:
  • Speaker name
  • Speaker email address
  • Speaker profile (max 500 words) including twitter handle, linkedin profile and photo.
  • Session type: case study, tutorial, workshop, etc.
  • Session length 45, 90 or 180 minutes (workshops should be 90 or 180 minutes)
  • Proposed track (iOS, Android, Cross Platform or Workshop)
  • Level (Beginner or Intermediate)
  • Session description (max 500 words)
  • Indication or whether you are happy to have your session filmed
If your submission is accepted you will be notified by the 15th of February 2014. Having a session accepted entitles the speaker to free entry to the conference and, if appropriate, free travel to the conference and one night’s accommodation booked by us. We hope to have as many sessions as possible filmed and published freely on the web. Please let us know if you do not want to have your session filmed. 

Topics

This year we are more specific in our requirements for sessions. There will be four tracks:
  • iOS
  • Android
  • Cross Platform
  • Workshop
We’re looking for up to three sessions in each track. Each session will be at either beginner or intermediate level. At the beginner level we’re specifically looking for ‘getting started’ type sessions for novice mobile developers. However, we will consider other beginner sessions. 

Type of Sessions

There are two session formats:
Presentation with slides
45 minutes in length, although double sessions will be available if needed (90 minutes)
Hands on keyboard workshop
90 minutes in length, although double sessions will be available if needed (180 minutes)
Participants for workshops are expected to bring their own laptops. Wireless will be available. Workshops will require participants to sign up in advance. If specific software is required speakers must make sure they allow time for this to be installed and configured or arrive early on the morning of the conference to help participants set up their laptops. A session the night before can be arranged if required. Please let us know if this is required when you submit your session.
All sessions must be entirely technical in nature. Any session that appears to be a sales pitch will not be accepted. 

Audience

Last year MobDevCon sold out it’s full capacity of 80 delegates (plus sponsors). This year our capacity is about 100 (plus sponsors). We attract predominantly developers, but you should also expect to find entrepreneurs, managers, testers, enthusiasts and all sorts of other people, even agents!
Please email submissions and any questions to: mobdevcon@nakedelement.co.uk.
Originally published on the Naked Element Ltd. website here.

Comments

Post a Comment

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

By
I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...
Post a Comment
Read more

Catalina-Ant for Tomcat 7

By
I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...
22 comments
Read more

RESTful Behaviour Guide

By
I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...
1 comment
Read more