Downsides: - if the software doesn’t get updated, you’re stuck running an old OS an old Mac that supports it. - you can’t just turn on the synth and use it, you need to find a cable, connect it to the Mac, launch the software, etc
571 karma · joined September 9, 2012
Downsides: - if the software doesn’t get updated, you’re stuck running an old OS an old Mac that supports it. - you can’t just turn on the synth and use it, you need to find a cable, connect it to the Mac, launch the software, etc
In the case of Google there’s a lot of internal reasons why they didn’t leverage this opportunity, but if they had done that they might have ended up making their main product even more sticky.
If you look at all the defining products of Apple, they also took years from the “germ of an idea” until they could be launched, and though they might have “shipped” internally, they gained a lot by not having pressure to ship things piecemeal to customers.
A lot of community building comes down to trust, whether you are developing a commercial or open source platform. As a customer and integrator/consultant/developer, I want to know that the platform is going to be around and supported. The bigger my company the higher the risk is.
Open sourcing your software sends signals to your customers and partners. Some will see it as a last ditch effort to make it successful, with the flip side being that if it doesn't happen, you're won't be maintaining it anymore. Will that make them more or less likely to use your software/help build your community?
So in your messaging you should be very clear in what you want to achieve, and how you plan to build a successful business around an open source or open core model, and how the others companies fit into this. How will you respond if another company takes your code and does the exact same thing you're trying to monetize, only better? Etc.
You should also be careful about positive feedback. Most people like to be nice and supportive, and won't say negative things. The only way to know whether you'll have success there is to see actual commitment (in money or work spent) with your product.
Finally as others have said, you shouldn't expect automatic success/community by open sourcing the code. You might end up attracting the sort of customers / developers that have the least incentive to contribute or pay for additional services, unless you go find those yourself.
But as you say, the company structure, market position and a lot more worked against them (same thing with Nokia and Symbian).
I wanted our employees to be able to roam to that meeting room transparently without any hassle. I knew that OpenVPN had a layer 2 tunneling mode, that could bridge two ethernet networks over VPN. With two leftover workstations, I set up an OpenVPN server in the main office, and an OpenVPN client at the meeting room. By bridging the OpenVPN interface to the ethernet interface on the client, I was able to connect a switch, WiFi access point and videoconferencing equipment. Everything worked perfectly, with even DHCP requests going over the VPN.
The one we picked had good API docs, but we didn't read the fine print - API access was a high yearly fee, costing almost as much as the regular subscription fee.
Their web interface functionality for importing orders/invoices from a CSV file, and looking at the browser requests I could see they were simply using the API in their frontend. A couple of hours later, and we had our invoice import job doing POST requests to their login page, getting the right cookies back and uploading invoice files.
Worked fine for years, only requiring a couple of updates when they changed their login page.
(Last time I checked, iPhone doesn't _require_ an iCloud account to work, although it still needs to "phone home" to be activated on setup.)
When terraform fails, it's typically because of a an API error or a configuration issue that is beyond its control?
Not handling state rollback is a design decision that, having dealt with the fun of CloudFormation, I'm pretty happy that they made.
Rubinstein saw the drive and realized that the price level and size was perfect for their product idea. And he had buy-in from the higher ups so they could negotiate a certain volume and price that made the project feasible.
That doesn't mean another company couldn't have been successful with a smaller 1GB drive (seeing the success of the smaller iPods later on) or a physically bigger 5GB drive (people were still carrying around walkmans and CD players).
What Apple managed to pull off was making a device that was easy to get music into (with iTunes) and easy to use (with the clickwheel) and, yes, compact and with good design and marketing.