Apple should buy Twitter, and they should do it now
patrickbgibson.tumblr.com
patrickbgibson.tumblr.com
What? Seriously? Apple should acquihire Twitter?
> The social network is basically an added bonus.
I think we're done here.
1) This guy is not a part of* Twitter, so he knows nothing about what Twitter's situation is from the inside.
2) This guy is not a part of* Apple, he has no idea about what Apple's budgets and plans and areas of interest are.
If I were an executive from say, the buyer, that is Apple, give me one good reason why I should listen to this guy's advice?
Writing controversial headlines is good for pageviews, but if you don't know what you're talking about, you might as well not create a stir in an otherwise peaceful community.
(*part of = part of the organization)
Twitter and Apple exist in the public sphere and they have many stakeholders. The public regulates corporations on many issues (down to the local planning board) so to limit discussion of a corporation to only those on the inside denies the reality that they have effects on the outside.
To take an extreme example: Nader and his book Unsafe at Any Speed.
Twitter and Apple are integrated in our lives (some more than others). Like Luther nailing his Theses to the church door, creating a stir is sometimes necessary.
To say one shouldn't create a stir seems conservative - if not defensive.
(If the author owns one share of Apple would that give him the right?)
I am not defending the piece as some monumental treatise.
BUT...
by this argument, an environmentalist asking for protection against pollution could be dismissed by a CEO who claims the market for pricing those externalities can't/aren't understood by those outside of the shop.
And...the corporation today could be easily compared in its breadth and omnipotence to the church of the 16th century.
* Apple can’t update its online store without taking it offline first.
In my experience it's a minority view that Apple are unable to do this. It seems more likely that it's a pure marketing decision, built around Apple's very successful hype machine approach.
For all of Apple's failings it's a stretch to suggest that they aren't technically competent enough to build an online store.
It this opinion common? Trying friends' iOS devices, I can't say I've ever thought "gee, this is so much prettier than my Android phone".
I still love it, but it's got a way to go.
The only time I've seen it amongst Android devs is for that alarm clock app [1], whereas it's a regular talking point about iOS apps (the latest being Paper discussing their colour-picker [2]).
[1] http://dewith.com/2012/an-android-design-process/ [2] http://www.theverge.com/2012/10/31/3578672/paper-1-3-color-p...
Granted, the community is smaller and the starting point is substantially lower (e.g. getting developers of iOS ports to read the Android design guidelines in the first place), but it is the same kind of culture.
Things aren't perfect, but things are getting better and we are starting to see a community come together that wants strong, high quality design.
When I use Android it feels like it puts a lot of flexibility and choice in my hands, that I can probably do more with it that I can with iOS but that there's additional work involved in that, both in that customisation but also the small amount of additional drag that comes with the additional choices available.
When I use iOS it feels like there's more simplicity but if I don't like that simplicity then tough. Don't like the iPhone? Tough. Want better integration between apps and services? Tough.
Personally my position right now is that I want iOS (I have kids, a job, a house and a million other things that take time and I have no additional bandwidth to invest in getting something just so, even if there would be benefit in doing so).
Ten years ago that wouldn't have been the case and I'd have found Android a more compelling choice and would have revelled in the flexibility, the handset options and everything else.
But overall that choice seems good for all of us. Better two visions offering genuine options than two identakit versions of the same thing, or worse still one monopoly player and no choice.
I hated android based on my experiences early on. Then I tried a Galaxy Nexus on ICS. Almost overnight I dumped my iPhone and switched.
The Nexus version of Android is what it should be. It looks great. It's clean. It's functional. It's even better than iOS is.
If Android devices weren't blocked from receiving software updates and the stock Google experience was the default, Apple would have a much tougher fight.
Here's where the article lost me: "They (Twitter) own scale". Seriously, Twitter has gotten shaky under load despite not doing push or even live updating its web page (compare this to Facebook's timeline).
For that matter, iTunes represents scale on a level unimaginable to Twitter. How much data does the writer think Apple is vending to support all the on-demand video, app purchases, and whatnot? Sure, iTunes goes down now and then, but so do Netflix and Hulu.
But there were a number of incorrect but less annoying observations beforehand. E.g. Apple doesn't NEED to take its online store offline to update stuff. It updates stuff all the time. Consider the rumor factory around Apple, I suspect the main reason is to stop folks spelunking the Apple Store constantly (especially during the lead-up to announcements) -- which they do ANYWAY.
You can make oodles of money off of crappy infrastructure[1]. The fact of the matter is that Apple's web services really are terrible – especially from a developer's perspective. Why do I have to use Apple's tools to add a device to my iOS Developer account[2]? Why isn't there an API for retrieving reviews for my apps? (Yes, I know about the RSS feed – it's terrible and currently broken once you get past page 10.) Or app rankings? Why isn't there an API to retrieve my app sales reports? Why isn't there an API to iTunes? (Yes, I know about the Enterprise Partner Feed – that's not the same thing.) Don't even get me started about Radar, their bug reporter[3]. The list goes on and on.
1. The infrastructure isn't necessarily "crappy" for them – it apparently works well enough for them internally. The problems begin once you try to interface with them as a third party.
2. There are some web scraper tools that allow you to do this, such as @mattt's Cupertino: https://github.com/mattt/cupertino/
3. bugreporter.apple.com
- No API for app reviews? Business decision. - No API for app rankings? Business decision. - No API for... you get my point.
If apple saw a reason to have these things, they'd have them. Blaming the WebObjects stack just _doesn't_ make sense.
bugreporter.apple.com? I'm with you, it needs to go the way of its 10 year old capsule buttons.
Payments has the potential to be a multi billion dollar business for them if executed correctly.
The cloud stuff doesn't make money. Apple is (or was, when I was there last) an extremely profit conscious organization. The reason that the various previous internet initiatives were failures is not because Apple can't hire good engineers, or uses yesterday's technology, but rather because no executive was going to make it to VP by spending a bunch of money and more importantly engineer time on something that by design loses money, and has only the vaguest connection to driving adoption of hardware.
This latter has certainly changed -- if the OP has noticed that Android "Just Works" in ways that iOS doesn't, rest assured that Apple knows.
Jobs would agree.