Cupcake is catastrophe, claims Big in Japan dev

[Chris Davies]

Everyone's looking forward to Cupcake, right?Â* Not so fast, says Big in Japan - the team behind the popular Sho... Read more

[LazyGenius]

all over the news today arent we AC?

but i kinda saw this coming... when alot of my apps werent compatible with cupcake i knew that all of them would be updated... but what about the ones that were pulled from the market or were discontinued, that im still using?(im still using the original "force ring" from back in the day)

curious to see how this turns out...

[DrVeronica]

my my that cupcake looks tasty there


anywho, not really surprised...anytime something new comes out, there's going to be compatibility issues.

[jroid]

why are ppl saying cupcake has been rushed?? everybody has been waiting for cupcake to drop for months now. it was added to the master branch a while back and devs still don't have their apps ready for cupcake, then when it finally gets released devs and ppl say it was rushed?????? i in part understand them, what google should have done was release the official sdk first a week or 2 before rolling out cupcake. but still there are apps in the market that were cupcake friendly even way before cupcake was released.

[DrVeronica]

lol cupcake friendly


they are saying b/c they're mad that their flashlite apps aren't working now

[Scythe]

why are ppl saying cupcake has been rushed?? everybody has been waiting for cupcake to drop for months now. it was added to the master branch a while back and devs still don't have their apps ready for cupcake, then when it finally gets released devs and ppl say it was rushed?????? i in part understand them, what google should have done was release the official sdk first a week or 2 before rolling out cupcake. but still there are apps in the market that were cupcake friendly even way before cupcake was released.

It's rushed because we just got an SDK to test our apps on. Let alone we can't version our apps for multiple SDK's. Basically Google's releasing an OS in which users expect apps to just work, even though there's fundamental structure changes many apps will have to make or they'll crash.

Specifically the apps that access system controls like wifi, have heavy UI elements, etc. (a lot of what ShopSavvy does)

Also dev's that update their apps for 1.5 right now that make use of the new uri's and similar, will crash out for the rc33 users. This should work like a regular software repository, where dependencies are listed in the package to avoid this issue.

Out of all the roll outs I've been in, this is the worst thus far.

[happyandyv]

lol cupcake friendly


they are saying b/c they're mad that their flashlite apps aren't working now

Without even reading into what they had to say I have to bet that you are right on this one.. Marketing lol....

[scrannel]

I imagine the biggest disappointment, from what I'm reading, are the known issues not being addressed. There are issues that should be addressed and those that must be addressed.

The must list includes:

Data transfer by Bluetooth; (needed it this weekend)

Functioning wifi; (need it 90% of the time)

Email that works for IMAP and POP3; (need all the time)

Ability to receive and download ALL attachments on the phone (email). (Need often)

Ability to stop ALL data roaming and keep apps from over riding. (When traveling, need all the time).

I have been told by several developers that Android/Google are well aware of these issues, so, that excuse is BS. These are abilities everyone has come to expect on any decent smartphone. I love the physical form of this phone, but ya know... this is 2009. When I was talking with a TMO tech she got into this real kinda cooing voice and said to think of the Android systems as a new born baby that needed lots of love and understanding. (Seriously!). All I could think of was that plastic baby from Blade Trinity with "**** You" written on its stomach, that spit raw garlic into your eyes.

[happyandyv]

It's rushed because we just got an SDK to test our apps on. Let alone we can't version our apps for multiple SDK's. Basically Google's releasing an OS in which users expect apps to just work, even though there's fundamental structure changes many apps will have to make or they'll crash.

Specifically the apps that access system controls like wifi, have heavy UI elements, etc. (a lot of what ShopSavvy does)

Also dev's that update their apps for 1.5 right now that make use of the new uri's and similar, will crash out for the rc33 users. This should work like a regular software repository, where dependencies are listed in the package to avoid this issue.

Out of all the roll outs I've been in, this is the worst thus far.

Do we know what changes google plans to make tot he market structure? People can't be trusted to know what version their on so.. It's not liek they can brake it down by version categories for devs to select between.. This sounds like a really major problem.. That samsung I saw grafted into an NES controller this morning is starting to look really good right now ;-)

Anyways - I hope they have some plans for that because... well that is just going to screw a lot of devs and put a really NEGATIVE opinion/feeling on the overall usability of the market..

[LazyGenius]

Do we know what changes google plans to make tot he market structure? People can't be trusted to know what version their on so.. It's not liek they can brake it down by version categories for devs to select between.. This sounds like a really major problem.. That samsung I saw grafted into an NES controller this morning is starting to look really good right now ;-)

Anyways - I hope they have some plans for that because... well that is just going to screw a lot of devs and put a really NEGATIVE opinion/feeling on the overall usability of the market..

palm pre FTW??