Look inside building an open source map app | Opensource.com

Look inside building an open source map app

Posted 18 Aug 2014 by 

Rating: 
(11 votes)
Image by : 

opensource.com

submit to reddit

Imagine yourself walking down the middle of a crowded street in a complex city like Cairo. Suddenly a protest builds ahead. A mass of people, cutting off the road. You try to evade, but then violence breaks out in mere seconds. You need help. Someone else, a car to get you out. A phone call might suffice, but wouldn't it be easier to notify all your friends that this place is dangerous and that you need their assistance? This is where a map-based social network could come into play.

There are other, less extreme uses for an app like Bird-I, to manage your location and your friends on a Google Map. Our app, that is still in development, hopes to make it possible to locate and navigate to one another as well as create SOS alarms in emergency situations. Birdl is designed with the help of the open source community and free technologies, and it is open for download and further editing under the CC BY-SA license.

Development of the application has gone through many levels of trial and error. Ultimately, all our trials were extremely valuable for the team. Our development team went through the following phases over a three month period:

  1. Android-based interface and webview to support Google Maps extension
  2. Systems database that would store:
    • User login info
    • User personal info (optional)
    • User history (optional)
    • User location schedule
  3. Login, registration, user settings
  4. Proximity notifications when a user is close to friends
  5. Event handling and navigation
  6. Handling traffic and danger alarms
  7. System validation and testing, extra features, iOS development

Lessons learned? They can be summarized as:

  1. Never lose your originality. Try your best to architect the software with a unique structure. Essentially, print your own thoughts into code. This includes the graphics used, the music, and everything else in your program.
  2. Simplicity gives birth to complexity. Any project, no matter how big it is, is composed from small concepts linked together. Master the small concepts to reach the bigger ones.
  3. Ask for help. Take the advice of any programmer you know. Don't give up when you can't translate your thoughts into code. Somebody might inspire you. This being said, don't paste others' code; use their advice as an inspiration for your own thoughts.
  4. Get your fuel. Without the proper goal, your project will probably fail. The fuel for our project was simply the aim of helping people, either by giving the source code as an educational model, or as an app for reaching friends easily in times of need.
  5. Don't be afraid to share your secrets. Inspire others with your work from time to time by sharing it with the world.

Each project has a starting point. Without the proper material, getting stuck in an infinite loop of confusion is likely. Our team found salvation in the form of open source material and help from programmers all over the world who were ready to give advice and share their experience. We want to pass it on, so here are the three main tips we learned for working in the open source community:

  1. Know what you're asking for. Don't waste the time of others with questions that have already been answered.
  2. Don't seek information from the community before making sure that you read the documentation.
  3. Don't waste the time of any single group or person. Try your best to ask around from different people so you don't overload others.

The conflicts a society faces are dynamic, so we hope an open source app like BirdI could be a good way to overcome them. And because the features can be freely extended, the ability of the app to solve conflicts can be even greater.

submit to reddit

2 Comments

mark23

Why Google Maps and not OpenStreetMap?

Vote up!
2
Vote down!
0
BirdI Team
Open Enthusiast

I had way more experience with google maps, and project time was pretty tight so there was no discussions at all about a substitution with the supervisor & the team. Self studying OSM from scratch would've extended the project time, and that threatened me with either low grades or failing.

Vote up!
0
Vote down!
0

Comment now