This is how they do in Indian railways. We book tickets. If it's full, we get waiting list number which will be confirmed a day before or on traveling day. If not confirmed, it will be cancelled automatically and refund sent to your account.
Try releasing your tools in public if allowed. Use the public datasets like in opendata.gov.in to create analytical reports for specific sector like fmcg. Use the tools and report for consulting and training teams in those sector to use the data.
I just spent whole day yesterday trying to upgrade RN0.40 -> RN0.42. It's a nightmare because there are conflicts in xcodeproj file and you have to manually merge them.
It sucks. Their default upgrade tool does more harm than good. Currently I start a new RN project then do a diff to see what I have to update on our actual app. Fun, right?
When Google maps came, we said the same. It won't work in India. There's no order in door numbering or Street names. They have to use landmarks and all that. But that's what Google did. In the driving directions in India, you can see lot of landmark references. We always underestimate what a tech can do. I am hoping we are wrong on this one too.
I was a kid when Google maps came, so I won't be able to comment on that. Self driving cars will work, nobody is doubting it, what I am doubting is the extent of self driving car, yes, in US like streets where everyone follows traffic rules it'll work without a person in driver seat, in India it'll be difficult for a truly self driving car like Uber is betting
Google Maps launched in 2005; if it works in India now, then it took at most 11 years more to get it working in India than in the US. That's not that long. Self-driving cars are more complex, but it'll happen eventually.
Develop a prototype app for your targeted customer.
We developed prototype android app with data in JSON included in apk. We showed it to prospective clients and landed project.
Thanks for the comment. I try to make my proposals in detail - include designs of the app that we're going to build. I haven't tried the prototype approach - I might try it next time. Just to be clear, you develop the prototype for the client's app, right? You would need access to the client's APIs, etc. which you might not have in a sales phase. I think using mock data is another way around this,
Follow up question, when you develop this prototype - In cases where the app is not very big, doesn't the client think that almost 50% of the work is done and hence may try getting this done in cheap?
We hardcoded the data in the JSON. Just show the potential. They may not know the exact requirements for the app. Also showing running app in real phone opens lot of opportunities.
My email is in profile. Ping me if you want to chat.
When you do consulting, you create asset for the client. But in side projects the asset can be yours. And assets may grow in value compared to consulting revenue.
