Skip to main content

Naked Element Ltd. presents MobDevCon: Call for papers


Conference: 3rd July 2013
Submission Deadline: 1st April 2013
Where: Hethel Engineering Centre, Norfolk

If you would like to be kept up-to-date about MobDevConf, please join our email list here and follow Naked Element Ltd. on twitter here.

Call for Papers & Speakers
Naked Element Ltd. presents MobDevCon (website coming soon) the first Mobile Development Conference in Norfolk. The conference will be held on Wednesday 3rd of July at The Hethel Engineering Centre near Wymondham in Norfolk, UK. Naked Element would like to invite proposals for sessions.

The keynote has already been confirmed:

  • Neil Garner of local company Proxama, speaking on NFC (Near Field Communication)

Submissions should be made by the 1st April 2013 to paul@nakedelement.co.uk and include the following information:

  • Speaker name
  • Speaker email address
  • Speaker profile (max 500 words)
  • Session type: case study, tutorial, workshop, etc.
  • Session length 45 or 90 minutes (workshops should be 90 minutes)
  • Mobile platform
  • 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 1st of May 2013. 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 all sessions filmed and published freely on the web. Please let us know if you do not want to have your session filmed.

Topics
We welcome submissions on any subject related to mobile development. We’re looking for beginner and intermediate sessions on Android and IOS as well as other popular platforms, cross platform technologies and web based mobile apps. However, please do not be limited by this, we’re happy to consider any mobile related submission.

Type of Sessions
We would like to see two main 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
    • Max audience size of 24 or 16 (to fit the workshop rooms available)

Participants for workshops would be 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 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
MobDevCon has a maximum capacity of 80 delegates (plus sponsors). We expect to attract predominantly developers, but you should also expect to find entrepreneurs, managers, testers, enthusiasts and all sorts of other people, even agents!

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

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...

Catalina-Ant for Tomcat 7

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...

RESTful Behaviour Guide

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...