IKEA Uses 3D Rendering, Not Photography, For Its Brochure Pictures
IKEA trained its photographers in 3D modelling and its 3D artists in photography. This was something I didn’t expect from a flatpack furniture company.
IKEA trained its photographers in 3D modelling and its 3D artists in photography. This was something I didn’t expect from a flatpack furniture company.
Every year, it is reported that Apple is facing production problems with new products. With Apple’s relentless push to adopt new technologies at immense scales, like the single-layer backlight mentioned in this case, it’s not really that surprising that they frequently have issues. However, as long as Apple is equipped to deal with such problems (that they must expect), there isn’t really a “problem” at all. Given the iPhone’s consistent release cycle, I think you can say that it is true.
The model identifiers are puzzling. The current 5s and 5c goes up to A1533 and A1532. It would make sense for the the device labelled ‘A1586’ to be somehow next-generation (as it is significantly beyond the 5s and 5c identifiers). The specification of the A1524 model number is much less obvious. Painting by numbers, as it were, the A1524 should closely resemble an iPhone 5c.
Gurman speculates that the model number could represent variants of the iPhone 5s and 5c, such as antenna tweaks, which probably makes the most sense.
A bit random timing for this to come about, but I suppose it is a good thing for all this to end. It’s slightly strange to me how the two companies continue to fight in the US though. Assumedly, the US is the market with the highest number of affected devices, making it worthwhile to continue chasing royalties and such.
Let’s hope this doesn’t flare up again in two months, when Samsung and Apple inevitably steal from each other for their wearable products. From what I can see, this agreement doesn’t preclude that from happening.
I don’t believe Apple expands capacity by an order of magnitude merely for future-proofing reasons. Adjustments to user growth happen gradually, not in one burst. My guess would be that this is for video content tied in with some new Apple TV (or iTunes Movies) initiative. Bitrates for high-definition video content are high enough to explain such increases in CDN bandwidth potential.
You have to be efficient with your time to make good ROI’s on the App Store. I think that is a much more important than what app pricing model you choose. Betting on apps of incredibly large scale means you bear proportionately more risk, with the possibility of no return whatsoever. If you want to maximise your profitability, make small apps that do a few things well. The amount of effort you put into an app has very little to do with how much of the market will buy it. This means that making big apps exposes you to substantially more risk, which is not fairly counterbalanced by significantly higher earnings potential.
In my opinion, you make money on the App Store by selling small things — it’s very nature is a bitesize marketplace. This is how you maximise your effective hourly wage. This doesn’t mean you have to turn around crap. You can still output quality pieces of software. Pour your heart into something for a short while (a month, maybe three), then ship it. Make your easy money (the first couple of weeks of sales). Iterate until interest dies away. Work on something else. Repeat. If something becomes a smash hit, then by all means develop it.
Unread is the complete opposite of this, it’s a beast of an app. It took Sinclair a year of development time. As a result, Unread faced massive risks when it finally shipped. Recouping months of development time is a lot more painful than recouping weeks of work. Sometimes you will get lucky, often you won’t.
I made Writing Aid in under a month, on and off. Thankfully, it sold well and produced a fantastic sales to hours ratio. Imagine a scenario where it didn’t do that well. I would have essentially wasted a month of work … but that is a hell of a lot better than wasting a year of work. You hedge your bets by moving fast and moving on.
Sinclair is annoyed that he formed a band and made a (well received) album that doesn’t earn enough for him to live a life as a rock star. I think indie devs should make songs, not albums.
I’m not quite sure what ‘beating Amazon at its own game’ entails, but from the outside, iBooks has always seemed like a runt in the litter. Apple pays as much attention to books as they do podcasts, yet they push iBooks as a mainstream operating system feature. Crucially, books costs money. Users expect more from stuff that they pay for and today Apple doesn’t really deliver.
One little known fact is that the iBooks app was developed very late in the iPad cycle. What was demoed in January 2010 was built in the last couple months of 2009.
Twitch announced a competing SDK in March, although it doesn’t seem to have anywhere near the adoption that Kamcord has attained. It’s just another example of mobile being an equaliser for new entrants and incumbents. Twitch may be the largest video streaming platform for desktop games, but it hasn’t been able to translate that into mobile streaming dominance.
This is a really cool video. It’s closer to an iPod commercial from a decade ago than anything Apple has done recently. I think part of the brilliance stems from the fact that the ad focuses on the stickers, an accessory Apple doesn’t even sell. The laptop is almost an afterthought, a given. It states ‘we are on top’, in a way that doesn’t feel boastful or brash.
This feels like something Passbook should start with. Everyone with an iOS device has an iTunes account, so everyone can get some form of utility out of this pass. It would stop Passbook from being empty by default.
Kuo is probably the most accurate ‘analyst’ there is for Apple’s product pipelines. Although the headline of this report is about timing (mid November rather than October), I’m more interested in what Kuo has to say about iWatch features. The release window is basically known at this point: September, October or November.
As such, I am happy to see that Kuo thinks waterproofing is a focus for the product. For me, I want to be able to do washing up without having to take the watch off my wrist for fear of it breaking.
Although this helps to justify the app’s permanent existence on the Home Screen, rather than a deletable option, Health still remains an obtuse mess. Everything isn’t very human. It’s confusingly technical.
You click on the Steps chart, for example, and it takes you to a table view of individual step entries. What is this purpose of this screen for end-users? Users can’t parse that list into anything meaningful.
Moreover, every nutrition category has an ‘Add Data Point’ option. This is equally stupid. People don’t know this information. Humans need sensors to tell this information. Having a manual input option is useless and only encourages cheating: I can tell Health.app that I walked a billion steps and it doesn’t complain. In fact, even the label of the option (“data point”) is uninviting and unnecessarily technical.
Right now, Health.app feels like a backend portal for iWatch debugging rather than the consumer-facing fitness and wellbeing dashboard it should be.
First buses go cashless, what next? It’s no wonder Apple (and everyone else) is scrambling to dominate mobile payments.
I get the ‘bulk-buy education cost-saving’ argument. There’s nothing wrong with Apple offering an iMac at cheaper price points. What I think is wrong here is that Apple was too stingy; the $1099 configuration has disproportionately poorer performance for the cost savings it offers.
A CFO doesn’t say something so blunt this haphazardly. How bad can Samsung’s performance be?
It literally is a MacBook Air with a 21 inch display; soldered ram, integrated graphics, mobile CPU. The standard configuration lacks an SSD, though, which means the Air is probably faster than the iMac in a lot of cases.
I really don’t get this machine. You take on a lot of compromise to save $200.