Coming Up With Ideas For “The Next Big App” By Solving Real-World Problems

Mobile (iPhone / Android / Windows) Apps can be utilized to solve communication problems.

  • Suppose two persons, A and B, share the same route to work each day. We can develop an app that helps them connect and share a car.
  • Or we can develop an app that connects used textbook sellers and textbook buyers (bit like Chegg [1]).


So if a group of people share a common interest or can be connected to solve a problem (but they are not friends on Facebook or not in one anothers’ contact list and not aware that they share the problem), then we can design apps that connect them and solve the problem.

Your app has to solve a narrowly focused problem and solve it well.

Uber, Airbnb follow the “Finance” Model.

Some people have excess of some resource and others need that resource. So the resource is being transferred from the provider to the needy “for efficiency” “on some conditions”.
In Finance, it’s transfer of money, through Banks, Bonds and Stocks.

Some people have excess of money that they don’t know how to make best use of. Others need money to bring a product to market or buy a house. So, Banks collect money from people who have excess of it, and lend it to borrowers who need it.

  • Uber [2] – transfer of ride space.
  • Airbnb [3] – transfer of house space.


So what are your ideas for the “Next Big Smart Phone App” that really solve real world problems?

Successful Apps

Android Application Architecture

AndroidManifest.xml file holds all of the different components of an Android Application together. 

The four main components of an Android Application – 

  • Activities 
  • Services 
  • Broadcast Receivers & 
  • Content Providers 

expose themselves to others through Intent Filters in the AndroidManifest.xml file.


Intent brings Web mindset to Mobile Application Development.

Intent & Intent Filter are modeled after Web –

  • Categories
    • Describes where and how the Intent can be used. 
  • Actions
    • Web equivalent: GET, POST, PUT, etc.
  • URIs
    • Contains data that can be used as method arguments in the respective Activities, Services, Broadcast Receivers & Content Providers. 

Android runtime evaluates the available Activities, Services, Broadcast Receivers & Content Providers and dispatches the Intent to the intended recipient as determined by the runtime.

Android development is modular in architecture. Android developers build components (Activities, Services, Broadcast Receivers & Content Providers), use components developed for other applications and can let others use their components to build apps.