1,277 karma · joined October 4, 2008
https://github.com/bumptech/bump-api-ios
https://github.com/bumptech/bump-api-android
Email me if you have any questions: tg@bu.mp
Working out of the box is something that we demand and is the typical experience for an API user, both in the old versions and in the new ones. If it doesn't, then we are available on email and our Google Groups and respond quickly.
A concrete example of how we are always pushing the limit: greater than 90% of all matches are now displayed on the handset in less than one second from time the of bump.
https://github.com/bumptech/bump-api-ios
https://github.com/bumptech/bump-api-android
http://groups.google.com/group/bump-api
http://groups.google.com/group/bump-api-android
We love feedback. Please email us: api@bu.mp.
C is still necessary for a lot of people at scale.
Anecdotally, I find that the iPad size is great for a table/lap, but less great for holding, while I love the size/shape/weight of the Kindle2 for reading. I don't think any particular size will win out.
They are about as competitive as a 15" laptop is to a netbook: not very as they are physically quite different. The price difference reflects this.
As the thickness and weight of the iPad decrease, it will become less cumbersome and more natural. iPad2 is already a big step forward in the latter two categories: it is significantly less awkward to hold an iPad1 but still has quite a while to go.
Typing today on an iPad is slightly awkward. Good voice recognition could eliminate this in private settings.
When these physical dimensions diminish, input improves, and screen resolutions increase, the experience will converge towards that of a truly interactive notepad or piece of paper, thereby becoming much more natural.
msft -3.5% aapl -3.38% hpq -4.4% ibm -2.2%
lnkd: -14% djia: -3.75%
The user does not and should not care about where his or her application logic is being run so long as this device is affordable.
The vision you present adds questionable cost savings and substantial latency: (NY->SF->NY)/c will always take 32ms, best case. Taking this trip asynchronously instead will make sense for a very long time.
Apple understands that shuffling data between devices is a real burden to users, so they've attacked that problem instead of chasing an esoteric one.
However, there's no reason why this data should not be stored by default under the OS's "Data Protection" encryption as email is by default on devices where a passcode is set:
It was instead Series60 third edition, which included a WebKit browser and SIP support in 2006.
Afterwards, nothing happened... it was as if the company threw its hands up in resignation post-iPhone.