These guys put together a cool little simulator and you use it embed a single app into your article, thus forcing all 100k visitors to your site to DOS the thing??? Why not link to the site and let people hit it on their own, thus spreading the load out to a few different apps and giving the server a chance to handle your traffic?
I feel for these guys because TechCrunch did the same thing to us when they reviewed Twiddla. They linked a single meeting room, thus essentially sending 10000 people into one conference call. "wow, this is crowded." "who changed the page?" "why did my drawing get erased?"
It was a full hour of chaos before we noticed what they'd done and pushed a new build to specifically redirect traffic from that meeting to the homepage. Not that TC traffic is particularly useful in terms of long term customers, but guys, at least try to think about what will actually happen if you deep link stuff like that.
Meanwhile development of a true iDevice emulator is underway. Unlike XCode's iDevice simulator (it compiles the dev app for the host architecture [x86/x86-64]), this emulator is based off of ARM QEMU with lots of hard work going into emulating the iPhone's hardware. It directly emulates stock iOSes/apps.
That being said, it is ridiculous that there is no built in way to take screens of an app on an Android phone (like the power + home iOS combo). Since Android has the concept of a secure canvas (e.g.sensitive content), this should be stock.
Lack of easy screenshots makes it harder for normal users to blog about and help review and promote an Android app.
It's pretty mind blowing - when I was developing Yelp Monocle on Android the best way to get a screenshot was to _take_a_picture_of_the_damn_phone_ because the SDK screenshot utility read out pixels very slowly in a raster pattern and due to the jitter from the sensors this resulted in a screenshot that appeared as if you were fast forwarding through a video.
On my Galaxy S, Samsung has baked in Home+Back Button as a way of taking screenshots... though needless to say this combination is prone to error. It also doesn't seem to work on certain views.
This is very cool. I'd love to read more about how it works. I think they're running a dedicated iOS simulator for each app and streaming the user input/video output via Flash. Even their $60/mo plan has a limit of 10 simultaneous viewers, so I imagine it's pretty taxing on their hardware.
They must be capturing the output at some deeper layer though since OpenGL doesn't render (but it does run).
Maybe, except that these demo apps, Yelp, Hipmunk, etc. are probably seeing 100s of simultaneous viewings right now. I guess they could have racks and racks of mac minis.
I'm guessing they increased the limit for the demos for free. I wouldn't be surprised if a single machine could run a dozen or two apps simultaneously, if they were able to trick the simulator into running multiple instances.
Since you send them a copy of your iPhone simulator code, they must be running this on some kind of Mac OS X system, and giving you VNC-style access to the app.
I have needed this product for months now to demo my company's app for prospective buyers. This will allow our technical sales force (who are on PC's) to share this via GoToMeeting with prospects (we're a B2B in a very relationship-driven industry).
The idea is great but unfortunately the technology behind it is limiting. Since their highest pricing plan only allows for 10 simultaneous viewers it's not realistic option to embed it in a popular blog as a demo.
The pricing plans we've put up so far are definitely intended for agencies / dev shops that want to share apps-in-progress with clients. We know there's a lot more we could do with this, though - we're just waiting for everyone to tell us what they want before we add new pricing :-)
These guys put together a cool little simulator and you use it embed a single app into your article, thus forcing all 100k visitors to your site to DOS the thing??? Why not link to the site and let people hit it on their own, thus spreading the load out to a few different apps and giving the server a chance to handle your traffic?
I feel for these guys because TechCrunch did the same thing to us when they reviewed Twiddla. They linked a single meeting room, thus essentially sending 10000 people into one conference call. "wow, this is crowded." "who changed the page?" "why did my drawing get erased?"
It was a full hour of chaos before we noticed what they'd done and pushed a new build to specifically redirect traffic from that meeting to the homepage. Not that TC traffic is particularly useful in terms of long term customers, but guys, at least try to think about what will actually happen if you deep link stuff like that.