I Guess Jobs Was Right...

[kapolani]

Flash for mobile is dead...

“Flash was designed for PCs using mice, not for touch screens using fingers.”

“Flash is closed and proprietary, has major technical drawbacks, and doesn’t support touch based devices.”

“The avalanche of media outlets offering their content for Apple’s mobile devices demonstrates that Flash is no longer necessary to watch video or consume any kind of web content.”

“New open standards created in the mobile era, such as HTML5, will win on mobile devices (and PCs too). Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticising Apple for leaving the past behind.”

http://www.technobuffalo.com/mobile...s-the-end-of-flash-player-for-mobile-devices/

 

[Khartun]

I found it funny Jobs could bash anything for being proprietary.

 

[kapolani]

I found it funny Jobs could bash anything for being proprietary.

It is rather funny...

But, Apple didn’t favor its own proprietary plugin over Flash. There’s no QuickTime plugin on iOS either. Apple’s view was, and is, that there should be no proprietary web browser plugins, period.

 

[YosemiteSam]

Flash for mobile is dead...



http://www.technobuffalo.com/mobile...s-the-end-of-flash-player-for-mobile-devices/

I was waiting for you to post this. You keep trying to be an Apple tool don't you.

Flash will be replaced by HTML5. This has been known for some time. (part of the reason it exists in the first place)

Adobe made a financial decision here. They know HTML5 will replace Flash. They have known this for a long time. The reason they are stopping development of Flash on mobile is a simple one. When Flash was originally designed it wasn't designed for touch screens or extremely low power consumption. Mobile devices as we have today didn't exist when Flash was created.

Due to that, Flash's core is fundamentally flawed from a mobile device stand point because of those issues. That doesn't mean it cannot run on mobile devices. Android proved that in fact it could and run well enough to be an effective software media component.

The issue at hand and 100% reason WHY Adobe made this decision is because of HTML5 and the impact it will have on Flash as a whole a few years down the road.

Adobe isn't ending Flash development. Far from it. They are just stopping the mobile development because of the overhead involved in rebuilding Flash from the ground up to better support touch screens and low power consumption. (ie, mobile devices) It would be easily worth it if HTML5 wasn't a couple of years off. By the time they rewrite Flash to have core support for those two issues, HTML5 would be here. Money down the drain. So what is the point of continuing it's development?

Personally, it will be great when Flash is finally no longer needed. It sucks as a platform and has several issues beyond just those two. The problem is, HTML5 support today can't reproduce what Flash can do right now.

My Android device will support Flash for a few more years until HTML5 finally takes over. (Adobe even said as much) Your Apple device will be limited until HTML5 catches up. Yes, limited. HTML5 support today CANNOT reproduce everything Flash can do. Even Jobs knew this.

The only thing Adobe said is that they will no longer be expanding Flash's capabilities on the mobile platforms.

Flash sucks, but at least if I want / need to see something that is made in Flash. I can see it.

 

[YosemiteSam]

It is rather funny...

But, Apple didn’t favor its own proprietary plugin over Flash. There’s no QuickTime plugin on iOS either. Apple’s view was, and is, that there should be no proprietary web browser plugins, period.

I don't blame Jobs not supporting it on iOS. Quicktime isn't any better than Flash. It is absolutely terrible.

The difference between Quicktime and Flash? There are several other things out there that can replace Quicktime today. There isn't anything that can replace everything that Flash can do today.

 

[kapolani]

I was waiting for you to post this. You keep trying to be an Apple tool don't you.

Why so angry?

You sound like a ****** every time you bash Apple. Apple isn't evil. They aren't forcing people to use their products.

Due to that, Flash's core is fundamentally flawed from a mobile device stand point because of those issues. That doesn't mean it cannot run on mobile devices. Android proved that in fact it could and run well enough to be an effective software media component.

So, you agree Flash sucks then?

"Well enough" is a far cry from stating 'it just works'

My Android device will support Flash for a few more years until HTML5 finally takes over. (Adobe even said as much) Your Apple device will be limited until HTML5 catches up. Yes, limited. HTML5 support today CANNOT reproduce everything Flash can do. Even Jobs knew this.

I can't remember if I've ever had a problem with the sites I've visited on my IOS devices. It's a moot point, really, while surfing on my Mac since I use Chrome.

If it worked they wouldn't cancel it for 'financial' reasons. They are getting out of the mobile space because it IS a flawed approach - in the mobile and desktop space. I've had many a desktop browser freeze because of some Flash content.

 

[kapolani]

I was waiting for you to post this.

You need to get a hobby. Step outside. Smell the fresh air!

 

[trickblue]

I was waiting for you to post this. You keep trying to be an Apple tool don't you.

Flash will be replaced by HTML5. This has been known for some time. (part of the reason it exists in the first place)

Adobe made a financial decision here. They know HTML5 will replace Flash. They have known this for a long time. The reason they are stopping development of Flash on mobile is a simple one. When Flash was originally designed it wasn't designed for touch screens or extremely low power consumption. Mobile devices as we have today didn't exist when Flash was created.

Due to that, Flash's core is fundamentally flawed from a mobile device stand point because of those issues. That doesn't mean it cannot run on mobile devices. Android proved that in fact it could and run well enough to be an effective software media component.

The issue at hand and 100% reason WHY Adobe made this decision is because of HTML5 and the impact it will have on Flash as a whole a few years down the road.

Adobe isn't ending Flash development. Far from it. They are just stopping the mobile development because of the overhead involved in rebuilding Flash from the ground up to better support touch screens and low power consumption. (ie, mobile devices) It would be easily worth it if HTML5 wasn't a couple of years off. By the time they rewrite Flash to have core support for those two issues, HTML5 would be here. Money down the drain. So what is the point of continuing it's development?

Personally, it will be great when Flash is finally no longer needed. It sucks as a platform and has several issues beyond just those two. The problem is, HTML5 support today can't reproduce what Flash can do right now.

My Android device will support Flash for a few more years until HTML5 finally takes over. (Adobe even said as much) Your Apple device will be limited until HTML5 catches up. Yes, limited. HTML5 support today CANNOT reproduce everything Flash can do. Even Jobs knew this.

The only thing Adobe said is that they will no longer be expanding Flash's capabilities on the mobile platforms.

Flash sucks, but at least if I want / need to see something that is made in Flash. I can see it.

You're right in that it was a business decision... flash is a power hog and right now, phone makers are desperately trying to figure out better battery technology as 4G LTE is also a power hog. Put those two together and you have REALLY unhappy customers...

I went ahead and purchased a 4S as I personally think, after a LOT of research, that solid 4G technology and usability is about 18 months out. I'm throwing a lot of things into that mix. Widespread 4G LTE infrastructure, battery technology, html5, memory technology that's quickly approaching.

The jump to 4G is very much going to be a slower process, IMO. Kind of like 10/100 to 1g ethernet... still a ton of 10/100 out there...

 

[YosemiteSam]

Why so angry?

Not angry anymore. Jobs is dead.

I told you 100 times. My issue was with Jobs, not Apple.

 

[YosemiteSam]

The jump to 4G is very much going to be a slower process, IMO. Kind of like 10/100 to 1g ethernet... still a ton of 10/100 out there...

The answer today (IMO) would be dynamic frequency scaling like they use in today's CPUs.

Use G3 or whatever. If the users begins to use lots of bandwidth at a certain point, scale up to G4.

When the phone is idling and checking mail, Facebook, G+, Twitter, etc. There is no need for the phone to be connected at G4.

It should be a simple fix using technology that already exists. I can enable and disable G2/G3 now on my two year old Nexus One. Android already has bandwidth monitors built in. Just enable them to be able to switch it from G2/G3/G4 when needed.

 

[trickblue]

The answer today (IMO) would be dynamic frequency scaling like they use in today's CPUs.

Use G3 or whatever. If the users begins to use lots of bandwidth at a certain point, scale up to G4.

When the phone is idling and checking mail, Facebook, G+, Twitter, etc. There is no need for the phone to be connected at G4.

It should be a simple fix using technology that already exists. I can enable and disable G2/G3 now on my two year old Nexus One. Android already has bandwidth monitors built in. Just enable them to be able to switch it from G2/G3/G4 when needed.

While I agree with you, the problem now with switching is that for me, AT&T LOVES to switch over to the Edge network and take it's frickin' sweet time switching back to 3G... even when I am in areas I know are 3G...

Carriers would love to spread us out over different speeds to minimize bandwith...

Didn't I read where one of the carriers is in trouble for that? Can't remember right off bat...

 

[YosemiteSam]

While I agree with you, the problem now with switching is that for me, AT&T LOVES to switch over to the Edge network and take it's frickin' sweet time switching back to 3G... even when I am in areas I know are 3G...

Carriers would love to spread us out over different speeds to minimize bandwith...

Didn't I read where one of the carriers is in trouble for that? Can't remember right off bat...

I haven't heard about that. I have T-Mobile and their G3 coverage is spotty by my house. When I'm on the train heading into work, it goes from EDGE to G3 all the time. When I'm in the city it's usually always G3 though.

 

[trickblue]

I haven't heard about that. I have T-Mobile and their G3 coverage is spotty by my house. When I'm on the train heading into work, it goes from EDGE to G3 all the time. When I'm in the city it's usually always G3 though.

Actually thinking about it, I think it was a broadband carrier doing that... Cox maybe?

 

[TheCount]

I still remember staying after school to play flash games on the school computers, it was amazing back then.

I don't see why they needed to venture into the mobile frontier anyway, it's such a rigid platform that it would have been really tough work to get it to translate.

 

[casmith07]

Flash sucks

That's about all I needed to get out of your post, hahaha.

 

[Reality]

I don't blame Jobs not supporting it on iOS. Quicktime isn't any better than Flash. It is absolutely terrible.

The difference between Quicktime and Flash? There are several other things out there that can replace Quicktime today. There isn't anything that can replace everything that Flash can do today.

Apple didn't like Flash because it would act as an OS within iOS allowing developers to create flash apps/games that would circumvent the iTunes App Store preventing Apple from collecting their cut of app sales. Flash would also appear slow and sluggish on mobile devices which would make Apple's iOS and iOS devices appear slow when compared to other similar non-Apple devices.

Sam is right though .. Flash just happened to be in the right place long ago, when HTML was still just simple markup code, to fill a need. Java was supposed to be the miracle portable language but the interpreters failed constantly with reliability (I hate java) and flash just worked and made the web more entertaining.

The only surprise is that it has taken this long for an alternative to arrive and, again as Sam said, that alternative is HTML5.

#reality

 

[YosemiteSam]

Apple didn't like Flash because it would act as an OS within iOS allowing developers to create flash apps/games that would circumvent the iTunes App Store preventing Apple from collecting their cut of app sales.

THIS, is what Jobs hated about Flash. While he disliked the power and touch screen, that wasn't what kept Flash from iOS. It was the fact that he couldn't force developers to pay him for their games. The downsides of Flash on mobile were just the excuse! His real cause to dismiss Flash was MONEY!

Flash was literally a sandbox. Once the OS (in this case iOS) allowed Flash to run, it couldn't control what happen within that sandbox. If you wrote an AppStore app, Apple could control it. (including prevent in-app sales which Apple has now outlawed)

btw Reality. Java is better today that it ever was prior, (though still not what you really want) but think GOD Java Applets are practically dead! :laugh2:

 

[kapolani]

That's about all I needed to get out of your post, hahaha.

......