domness's comments

I wonder how effective this method compares to that of using something like binaural beats.

I'd certainly like to work on it if it went open source.

All my work is via Git. So in my team we use GitHub for our normal projects (pay per project), and when we're done, I put it onto BitBucket (pay per user), so whatever I put onto BitBucket is then free of charge. I think I'll stick to this solution as it's cheap (read: free).

However, if I was to use your service, I'd be happy to use command line.

Yeh, I think it's definitely looking more like Sublime Text.

Fancy, however, I still prefer things like http://e.ggtimer.com/ as it allows other functions such as a Pomodoro timer.

Well of course all that is done before all of the developing of the app. The idea is to reduce the amount of uncertainty by not creating a full blown app that has had a lot of time and money put into it, when some of the features aren't helping in terms of getting new customers, keeping old customers and bringing any value to the product/service.

Yes, TestFlight is absolutely great for beta testing.

However, in the startup sense, it's not exactly beta testing, it's testing the market, so beta testing would be fine to test something you've built works, but by no means will show what people will think of the app/product.

Well then you wouldn't be the early adopter :) The idea is to test it against early adopters who don't mind about these quick changes and are less worried about bugs, because the idea/product is something that's good enough to help you in some way, shape or form.

May I ask, what's proper market research? Considering you can get so far with "proper market research", but it definitely doesn't tell the whole picture. People often don't know they have a problem until one is solved and a good way.

Hmm, I think a lot of people are missing the whole point in this article. I do around 60% Ruby on Rails, 35% iOS and 5% Android dev. The idea around a "lean" startup being, that an MVP, or each new feature, or even testing a change to a previous feature is usually done in quick succession. This being testing with current users over a period of say, a week, and then from the results, changes can be made and the team have learned from the testing.

So really, Android allows for this quick succession of testing features and iterating as quick as possible, with even to a few hours turnaround. Also, that it would cost a lot in development time to get something "just right" for the App Store for it to be accepted, whereas with Android you can keep on iterating and pushing changes without having to spent a huge amount of time making everything look perfect, and be absolute minimal in terms of bugs.

I love iOS development, and yes, I agree with most people on here about the revenue from iOS, the people paying for apps, Apple's process of helping keep out most malware etc. etc., but for the sake of a "lean" startup, spending extra weeks testing apps making sure it's completely bug free and "looking good enough" for iOS, as well as the wait for Apple to accept the application (and then for users to download the update, in the case of iOS 7, this has been solved), Android is a much better dev option for these changes.

Of course, when the team knows that the app is something that people care for, and they have a decent knowledge of what users want, what features they use, and the kind of value that the mobile app brings to them, then they can go ahead and make the best possible iOS app.

TL;DR

Saving time, money and quick iterations, learning from customers and getting quick data for problem validation, is much easier and faster on Android, than the process on iOS. Think Lean Startup.

I don't think I've had an issue like that over the past couple of years in my Rails career.

I'm sure you should have probably understood why your code 'no longer works', perhaps some bad Ruby/Rails programming practices?

I've had a number of attempts at adding a "Buy it now" and some scammer from Nigeria (every time) ends up "buying it" and sending phishing emails. Only to have to wait again to put it up for sale after a few days.

For blogs on GitHub I use Jekyll. Seems to have quite a bit of support with some great plugins.

Starbucks!

Fine on the iPhone 4S

Indeed, the same over here.

Links just return back to the same page, and right at the bottom..

Pretty much agree with the author here. 2 housemates bought Android phones, only to have it full of apps that have slowed them down to a standstill and are now unusable.