As the app is a hybrid app, ready for its release only on Android platform, I am uncertain on how many will actually try it out when posted in Show HN. What do you think?
This indicates a dependency (on mobile devices) that is not inherent in the problem domain (following a page on Facebook). The dependency on mobile devices impedes the critical business function of receiving feedback from potential users. The app prototype could just as easily be a web page.
Overall, the app has a dependency on Facebook's API's and terms of service. Facebook can change theses arbitrarily or decide the app violates their intent.
Good luck.
1st dependency, dependency on mobile devices, yeah, I regret starting with the mobile app. Though this is a hybrid app, considering the time that I can spend on this and my pace, I might take nearly a month to make a web app. And now, I am not sure if I should go ahead and release the Android version, or work on the web app and release web app first. Any suggestions?
As a general observation, many successful apps have a website in addition to a presence in the app stores. So it makes sense to assume you'll be building a web page anyway. For an app like yours, it's probably easier to test and iterate core logic on a webpage than in a mobile device.
Whether it makes sense to build a web page at this point requires looking at the risk of the second dependency versus the cost of building a page and that's a business decision for your business.
[1]: http://venturebeat.com/2013/06/26/get-to-no-as-fast-as-you-c...