Bolo launched in 5 hours..

Bolo is a new app that I’ve created that helps parents record interesting voices to animal pictures and play them for their kids. Well, technically, the kids could do that too. So, all in all, fun.

It started on friday morning.. Was playing with my son and found some apps which make animal sounds. The sounds aren’t the best in most of those apps, to say the least. So I started making some noises myself and my son loved it. Well, the sounds were still not great, but he loved it being performed live. Hah, I’ve defended myself now.

Gave me an idea, why not make an app where parents could fill in for animal’s voices. Then start playing with their kid, making noises live and being played back. That’s how ‘Bolo’ started.

Bolo in hindi means ‘say’. So thats what it does.

Development started Friday night. Saturday Afternoon, it was pushed to the market. (Of course, I slept for a while too.)

Technical details :

Contains a simple ViewPager Activity and FragmentStatePagerAdapter. Recording and Playback is done using MediaRecorder and MediaPlayer apis. There’s not much to say apart from that.

It is available in Google Play Store here.

The pictures are taken from and modified using Instagram’s android app.

Hope you have fun with it. Do let me know if some addition could improve the experience.

Here are some screenshots:

Useful tools if you’re starting an android app.

There are a host of independent libraries which help us write android apps more quickly and in more maintainable fashion. These apps range from accessing View elements to Event Handling to Security and Database access. Here are a few of them which rate high in my opinion:

1. An actual smartphone

There’s nothing like it. I’ve seen few people code on emulator. I’d not recommend it because of its speed and irregularities. Start using the phone for your development. The productivity benefits are huge.

One handset would do fine for development. ūüôā

2. Robotium

Simple test framework on Android.

3. Robojuice

It has few good utilities like Injection of resources/views and pojos. Also has a basic event framework.

4. Sugar

[I’m the developer here]. But seriously, if you have more than a few tables, its better to go with a tool that provides you some abstraction. Sugar is an effort to provide ActiveRecord like access to database Objects. Few similar tools that offer this feature are listed here..

5. IntelliJ IDEA and MAT

IntelliJ IDEA is the best Java editor out there. Android support comes with its community edition. Memory Analyzer Tool is an obvious choice for analyzing the heap dumps.

6. GreenDroid

It has some readymade widgets for use in Android. The code is fairly mature and useful. Good addition to your UI development.

This in no way is an exhaustive list.. I’ll try to keep adding to this list with some specific libraries for specific purpose.


7. ActionBar Sherlock

Action bar is a great way to present navigations and user actions in Android apps. It was started with Honeycomb and is well received and extremely improved in ICS and Jellybean. ActionBarSherlock provides an easy way to make this design available on prior versions of android. Its very popular and a must-have library.

8. Sliding Menu

Its a nice little library to add sliding menu (like Google+, Facebook, etc.) to your application. It is very easy to integrate with and adds a touch of style to your app. Along with ActionBarSherlock, it adds a great look and ease of navigation to your app.

Do share if you have some recommendations.

The Bargain

We always do that in here. Its a way of life. Right from milk, snack, groceries, tickets, electronics, apparels, dowry, corruption everything.. Some legal.. and some illegal. But yes, there’s bargaining everywhere. So, our software industry is not far away.

This draws a very thin line between ethics and business smartness.. though, there’s nothing smart about it.

This is a constant struggle most of us face in a software Job. So much so that, its now an expected¬†behavior¬†between employees and employers. So one asks a question.. If you’re one of those self-respecting and introvert-ish souls, how do you tackle this situation? Frankly, we do not have an answer.. yet.

But, hey.. this is not just an employee’s problem. Its as much an employer’s problem too. In our profession, many engineers tend to be introverts, who’d rather leave a company than get into an argument with lesser beings (managers). So both parties suffer in this situation..

Lets try to analyze the situation a little.. The primary items for discussion tend to be around:

1. Salary (of course, guess thats not india alone)

2. Designation (Yup, explains all the nonsense designations that exist)

3. You guessed it.. Going Abroad.

Lets try to look at them at greater detail.

1. Salary

This is a no-brainer. There’s been a time in everyone’s career, where he’s had to negotiate for the salary package. Its almost like a game of wits between the employee and the employer. This happens at primarily two occassions:

a. During joining a company.. typically determined by the past salary, with a raise.

b. Salary review.. once a year, in most cases.

If you’re in one of those companies where Pay is determined by number of years you’ve served this army, well.. you can’t help much. Just got to serve your time or get out of there.

For others, typically, companies do not have a transparent and well-defined review processes. Lack of transparency means many questions are unanswered and things are manipulated around. This typically serves purpose of the Negotiators.

As a company, you need to be avoiding such cases. Let the recruitment and the review process be as transparent as possible. Always over-communicate in these situations. Do not leave a window for bargainers and negotiators to influence the decision.

2. Designation

Well, they found a solution to it. Invent a new one yourself. I believe companies would be going the route of “Invent your Designation” as an HR perk now. Lets leave this discussion before the Chief assistance Designation Discussion moderator stops us.

3. Going Abroad

This is pretty popular. Some do it coz they like to travel. Some, coz they like the extra money. I’m sure this is not the situation in Western Countries, but yeah..they have the reverse problem. No one wants to leave their place. Lets get back to the point.. This is one of the worst kind of discussions. There’s hardly any merit or logic behind this.

In a product setup, it’d make more sense when the engineers would like to get closer to a customer and understand the situations better. But, in other setups, its basically not related to work at all. In that case, its typically an arm-twisting affair. Or in some cases, act as carrots for the managers too.

Ideally, as a company you’d like to have your most appropriate person for the job to be sitting closest to the customer. That isn’t always the case. In some companies, they also have a round-robin way of selecting who goes next. The situation is rather sad.

As companies, you could make it fair by again making it a very transparent and objective decision. Do not use them as carrots. Do not advertise these things during recruitments. But it seems too ideal.

I understand that there’s no solution being suggested here. This is just an analysis of the situation. I believe it top companies want to attract and retain high quality developers and employees, they need to be solve it in their own ways and not let this nonsense creep into their culture.

As employees, well.. good luck.

The thing about strong opinion..

.. is that its just an opinion put forth strongly. This doesn’t mean its more appropriate ¬†or better than other opinions. Actually, it shouldn’t be treated any different than other opinions.

It generally depends on the personality of the person stating it. Some people are more subtle in their statements and some prefer to be more affirmative.

A correct and well thought out opinion, is slightly different. In the sense, it doesn’t only focus on the pros of the opinion. It also highlights certain drawbacks, and gives a logical conclusion where pros outweigh the drawbacks. They’re much more educated and the ones which should gain more attention.

Other thing about strong opinion is, its emotionally backed. Its a major drawback. Emotion doesn’t always go well with objectivity and reasoning. If the same emotion is not shared by others in the group, it generally goes unnoticed.

Its extremely important how you put forward your opinion in a group and how you appreciate opinions from other members. Give more weightage to objective ones. Try to avoid emotional ones and strong(loud) ones.

When you can’t differentiate..

How do you differentiate one work from another? The real involvement lies there.

We generally come across many people who’re statistics driven.

people who look at numbers and make future predictions..

people who look at some random percentages and make judgement on other folks..

people who read numbers and assume they know the story.

Well, a Dravid’s century is a lot different from Sehwag’s century which is lot different from a Steven Waugh’s century. But statistically, they’re only centuries. You can’t differentiate based on that.

For people who know less (or care less), those figures and stats are all they need to know.

For people who care, or really interested in stuff, they go beyond numbers. Infact, numbers don’t matter to them at all. They can genuinely differentiate one stuff from another. Good from bad, bad from ugly, what’s the next line.. nevermind.

When you can’t differentiate one person from another, one company from another, one music from another, and need stats to help you make decision, well.. you’re basically ill-informed and paralyzed in some way. Go get more information. Talk to people. Learn about things.

When you can’t differentiate, don’t make decisions. Either learn about it, or leave it to professionals.


Sugar : Android database made easy.

UPDATE : Some of the code snippets in the below post are outdated. Please visit for latest updates to the library.

This post is an introduction to Sugar library for android. The aim of the project is to simplify database access in Android.

The project draws inspiration from GORM for grails or Active Record for Rails. These patterns have been hugely successful in the web world, and have set a benchmark for libraries for database access.

The basic objectives of the library  are:

1. Creation and management of database and connection.

2. Simple and Intuitive API for database querying.

3. Simple CRUD operations.

Source Code

Source code is present at

You can clone it and start hacking. There’s a build script along with it to compile and generate the binary.

An example project using the library is present at


Android Manifest file: 

Include the android:name attribute in the application tag. SugarApp extends android’s Application and initiates the database creation for the project. By including the attribute, you’re basically starting with SugarApp instead of android’s Application class. If you intend to write your own Application class, you can extend SugarApp.

<?xml version="1.0" encoding="utf-8"?>
<application.. android:name="com.orm.SugarApp">

The entities need to inherit from SugarRecord including a typed parameter. SugarRecord provides for all the CRUD methods that will be available to the entity classes.

public class Note extends SugarRecord<Note>{
private String title;
private String description;
public Note(Context context){

Thats about it. Configuration is done. You’re ready to dive into the sweetness of Sugar. (OK.. I couldn’t stop myself from saying this.)

# inserting values

Note note = new Note(context, "Note 1");;

# query

Note.findById(context, Note.class, 1);
Note.find(context, Note.class, "title=?", new String[]{"Note 1"});

# delete
Note note = Note.findById(context, Note.class, 1);

# few more..

Note.listAll(context, Note.class);
Note.deleteAll(context, Note.class);

Nice.. All done. Happy Android hacking.

You can’t hide the bitter truth..

Yes. Sooner or later, it would come out.

It leaves you two ways to combat it. One, the cowardly way.. look away from it, don’t share it with people, hide it, punish people for revealing it, ¬†conceal it by any possible means.

Other way is to share it. Share it with all honesty. Show confidence in people.

The second approach gives you all control over the moment, the occasion you reveal the truth. The first one only manages to scare you and makes you repeat the same over and over.

In both cases, you’re unaware of the outcome. But in latter approach, you tend to control better.