Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/class.wp-dependencies.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-content/plugins/eminimall/eminimall.php on line 341
2012 January | Flash Enabled Mobile and Consumer Devices


Welcome to Embeddedflash.com. Its 2014 and the landscape in multimedia world has changed quite a bit HTML5 standard is complete and Flash is no longer existent on mobile. I've also taken a short break from blog but I hope to restart it in the near future. I am no longer functioning as Adobe's Scaling Partner and looking for new opportunities. If you are looking for a technically savvy, energetic business development, marketing or sales person, please email me.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

End of life for Flash etc…

Android, Desktop Flash Player, Flash 10, Flash 11, Flash Enabled Devices, Flash Lite ports, Operating Systems, Processors- ARM
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55
January 25th, 2012

Much is being debated about Adobe’s decision to end life for Flash mobile. Remarks have ranged from ‘didn’t Steve Jobs say so’ to ‘what the *#$$’ to ‘I feel like I’ve been let down by Adobe’ and so on. While I am sure Adobe has its own reasons, but in my opinion, it simply came down to ‘Return on Investment’. Now keep in mind, we are Adobe’s scaling partners. So our goal is also to make profit with Flash player (identical to Adobe’s), and have experienced every pain that Adobe has. In this capitalist world, goal of any business is to create ‘value’ in exchange of the ‘effort’ one puts in. In this case, it was just a matter of deciding whether the return on investment on Flash was worth the effort. Ultimately Adobe decided to follow route that would generate dollars as a business and in the process ended up killing Flash on mobile. ......continue reading