Skip to main content

Android Developers Day


We welcome everyone interested in Android. Come to Ankara and join us in June.
ADD (Android Developer Days) is now reloading for 2013. ADD 2013 will take place on June 14/15, 2013 in METU Cultural and Convention Center. ADD 2013 is targeted to be the one of the biggest international tech related organization in this region. ADD 2013 will have more participants, more fun, more networking and more inspiration. (The first ADD(Android Developer Days) was on May 21/22, 2012. There were 700 participants and more than 30 speakers.)
You can join the conference with the followings:
  • Presentations that is 15-20 minutes or 40-45 minutes long.
  • Quickie: 10 minute presentation in small rooms.
  • Poster: You can show your applications in a place dedicated for posters.
  • Workshop: Presentations with hands on coding, 40 minutes long.
Indicate your contribution in OpenConf and please indicate how much your presentation is going to take when submitting it to OpenConf Deadline of Call for Submissions is 1st May 2013.
Subjects:
  • Future Technologies
  • Mobile World
    • Future of Mobile World
    • New Generation Mobile Devices (Project Glass)
  • Android OS
    • Future Versions
    • Android in Different Architectures
    • Android in Different Areas(Industry, Defense, Home Electronics etc.)
  • Android App Development
    • New Features and Capabilities
    • App Development Best Practises
    • Android SDK Tools
    • UI(User Interface) / UX (User Experience) Design
    • App Monetization
      • Ad Integration
      • In-app Billing
    • User Statistics
  • Android NDK
  • Cross Platform App Development Frameworks
  • HTML5
  • Javascript
  • Game Development
  • Google TV
  • Google Playstore
  • Communication Solutions (NFC, Bluetooth, Wi-fi)
  • 3G, 4G Wide Band Communication
  • Cloud
    • Google Cloud Messaging for Android
    • Google App Engine
  • Augmented Reality
  • Social Media
  • Location Based Services and Maps
  • Mobile Education (Fatih Project)
  • Mobile Payment
  • Security
  • Arduino
  • Software Development Methodologies
  • Success Stories
  • GWT
Moreover we appreciate all different ideas and papers beyond subjects above.
Keep in touch ;)

Comments

Popular posts from this blog

How to change position of MyLocationButton on new Map API v2 - 2

In my previuos post[1], i mention a workaround for changing buttons on Google Map which we use with google services. It is good to know they listen developers and make their products more development friendly. (I hope it goes like that way all the time and all the product lines of Google) Now we have a method for setting padding of map. It is add padding to useful area of map. We can see full screen map but with padding we can use prefered area of it. It is good for overlay action bar and other things on map view. [ 2] They write a blog and take a video about it. Read blog and watch video if you are using google map in your app :) [3] And finally, They add this method because of this issue. That means, if you find a bug or want extra feature from and api, write to google via this issue tracking system. [1] http://blog.kozaxinan.com/2013/08/how-to-change-position-of.html [2] https://developers.google.com/maps/documentation/android/map#map_padding [3] http://googlegeodeve

Using Accelerometer when Screen Off

Introduction Android Phones have a lot of built-in sensor such as gyro, proximity and accelerometer. Using Accelerometer in Android is a known thing. For listening sensors, class or service needs a SensorEventListener implementation. An Activity is only exists when you are seeing it. When phone enters standby mode, activity which was recently active frozen and restored whenever needed. While this frozen time, activity doesn’t run. Because of that it doesn’t need sensor updates. And Android stop to listen some sensors for power management. Services have this condition like classes (activity). In contrast to class, a service run every time, even when phone is in standby mode. Therefore Services needs sensor updates for some situations. But android stop to listen some sensor(accelerometer) in some different phones. There is a solution for that. This is not an exact solution but it work with a lot of phones. With a BroadcastReceiver listen   Intent. ACTION_SCREEN_O

How to set alarm to show a notification at future date with AlarmManager?

Lets assume you want to do a job a future time or show a notification at a selected time. AlarmManager can help to send an intent in future time. First we need to select date, Lets create a date in 2050, Calendar calendar = Calendar. getInstance () ; calendar.set(Calendar. YEAR , 2050 ) ; Date date = calendar.getTime() ; For showing notification we need a service. public class AlarmReceiver extends Service { public AlarmReceiver() { } @Override public IBinder onBind (Intent intent) { } } Add service to Manifest.xml <service android :name= "com.kozaxinan.example.alarm.AlarmReceiver" android :enabled= "true" android :exported= "true" > </service> We will modify AlarmReceiver for sending notification. But first we need to register a alarm. AlarmManager alarmManager = (AlarmManager) getSystemService( ALARM_SERVICE ) ; Intent intent = new Intent( this, AlarmReceiver. class ) ; intent.putExtra( &q