I've found that many iOS applications implement their own syncing that works quite well (and the OS-level syncing of contacts, calendars, and mail works well). The mere presence of an iPad means I'm more likely to use that than my iPhone, saving the battery for calls. And finally, I'm not sure a tablet with a big phone-sized wart on the back is a net space savings, considering you're usually going to want your phone closer at hand (pocket) than your tablet (bag) anyways.
"Many" !== all. It relies on developers to roll their own syncing. On the other hand this product would mean literally anything on one device is available on the other, regardless of network availability.
On top of that, it is undeniable that one of iOSs strongest points is its lack of hardware diversity. You dont expect the sync your iPad with your droid, but should you expect to sync everything between your Galaxy Tab and your Droid X? If so, whose burden would it be? Samsung? Motorola? Google? the community? Or every developer of every app? This streamlines it a bit more. And since it only relies on the location of a couple of plugs, any oew could make it hardware compatible.
It makes the tablet marginally thicker, but the lack of necessity for a second charger already makes up for that.
I do not think the design is without its flaws, however I really do think that this is moving more towards the future than a dead end.
We have few business models in mind and monetization strategies. We will explore them as time goes on very carefully, but right now our goal is to make Minus better and increase compatibility for mobile platforms and more such as allowing documents and other filetypes.
This could mean instant death for MonoTouch. What developer would choose to write an iphone/ipad app in MonoTouch with the risk of having to re-write their app if apple drops the hammer.
Thats very true, but other app store policies aside, if your going to write a new app this might be enough FUD to completely rule out MonoTouch (which I was considering).
"... world of Children of Men, though." ah great movie. I almost cried on the scene where all the soldiers and the insurgents stop fighting to protect the baby.
Sorry to be so harsh but, the introduction of themes signals to me that the developers have thrown their hands up in defeat. The alternative is to improve the look and feel of the core design.
You guys have managed to rip off / borrow stackoverflow's look and feel ( which is good ) and moved the all text a few pixels off center, shade icons that were unshaded, resize GUI elements. If you going to take so many GUI elements, why not take everything?
But you offered themes as a solution to a statement about UI quality, which is it not. Also you don't have to do what your users ask for, saying no to bad ideas is important.
Your not alone, the chromium team should have said no to themes as well.
Well it's open source dude, if you think you can do better at UI quality feel free to give it a try. And thanks for the advice... Also, theming is a good features, not all out users want to have the same UI. They can also fully customize the CSS. And for the matter, SO UI is far from perfect.
I was too harsh earlier. The main point I'd like to make is that themes are independent of the core UI refinements that need to happen. Shapado faces 6+ months of work before it can have quality of SO.
I support open source software, but who is going to sit down and do this painstaking work. It's easier to work on theming or mongodb, rather than make the titles spaced correctly ( for example ).
SO has being in development for more than 1 year, during that time the UI has being under constant refinement. Lets see where Shapado is in 6 months, my guess is exactly where it is now ( GUI wise ).
