domness
Show HN: OmniFocus Web Interface
EA games web server hacked to host phishing website
Code review files side-by-side with GitHub Spectacles
Show HN: My iBeacon app built in a few hours
Show HN: Crowdsourced fundraising and sponsorship for sports clubs & teams
However, if I was to use your service, I'd be happy to use command line.
Show HN: A new startup of mine that is now available
Costs Saved when your Team Writes Automated Tests
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.
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.
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.
Show HN: Say hello to Bundlll
A Solution for a Distributed Team Problem
I built a pinterest for teams/clients/organisations
I'm sure you should have probably understood why your code 'no longer works', perhaps some bad Ruby/Rails programming practices?
Show HN: Bundlll - Your work is scattered across many online tools.
Show HN: Arrivals - Keep your inbox free from notification emails
Presentation: Lean Startups
Ask HN: Mongoid vs ActiveRecord (Postgres)
So we've come up to a point in our project where we are thinking, should we have actually used MongoDB? We are using it at the moment, but sometimes find a few gems don't have support for Mongoid and we often have to find a work around.My main thoughts are:1. Is using MongoDB actually any better in production?2. What are the pros and cons of using either one?3. If you were to create a new rails...