Posts Tagged Adobe
I have been reading about this an nothing I found was really expressing what I fell about it. The thing is I never really had a project that could benefit from using the opcodes. I mean I have built rich experiences for the past 5 years and some of my projects were pretty complex. Stage3D I would use, big time, but not to build some crazy 3D world, I don’t have the 3D skills for that. My point being, in the state that it is in I don’t think I would ever use the memory opcodes and I believe it is so for 90% of the developers out there. Now I know that on the Flash roadmap from Adobe they are planning to give easier access to the memory opcodes, maybe that will change my views on this, but it hasn’t been done yet.
Lastly, on the 9% thing, this is the amount of money you must give Adobe once you have made more than 50k revenues using Stage3D and the opcodes, I think it’s fair. I think the Unreal engine has a similar licensing model, where you don’t pay anything unless you have made 100k. If I ever come to have to pay the fees, it will be a problem that I will be happy to deal with as I will have some kind of success anyway. What do you guys think? Am I a senseless individualist bastard or do you agree that it is mostly the elite crying out?
Haha, yeah, haven’t wrote much lately, not that I don’t want to, I just don’t have anything to write about, but now Adobe did give me something. So, they will stop working on the mobile version of the Flash player. A lot of people talked to me about it this morning, with big grins in their faces, like saying: “See, see, it’s dead already”. Damn people are clueless sometimes, haha. I don’t think it’s that big of a deal right now, right now I mean, but I think it could mean way more in the future.
Ya, right now, on a phone, with its screen size, it is not the best way to consume Flash rich experiences like Aldo Shoes for Life. The screen is too small, you don’t get as much as what you get on the desktop. But the same goes for HTML rich experiences; would you interact with the Wilderness Downtown on a mobile phone? I don’t think so. Where I think it is more problematic, is on tablets, where the screen has more real estate. Most rich experiences would work pretty well on that. The problem is that the only tablet worth the name is the iPad (well that will change in time) so no one could see rich flash experiences on them and realize that it is working quite well.
So short term, no biggie, doesn’t really change much, nobody was doing Flash sites for mobile anyway. Long term, it’s hard to say. Phones are gonna get bigger screens that I am sure off, be it foldable screens or some other innovation, screens will get bigger. Also, there will be more tablets out there and their uses will be more defined. For that alone, it would be nice to have Flash on mobile. Then, there is the new mobile application paradigm, where instead of building web experiences and apps, you build native apps. I don’t know if this is a trend that will last forever. I mean the desktop is slowly moving toward web and cloud, shouldn’t mobile do the same too? So I think it might be a mistake to stop mobile development.
But I also understand a bit, I mean Adobe was already developing 3 Flash players : PC, MAC, Linux. Now with mobile, it would have to develop one for every mobile operating. So here it is, my views on the topic, one more in the sea of web.
I believe it should be the same with Flash. Every day you can see an awesome piece of creativity if you go to theFWA.com; sometimes you know how it is done, sometimes you don’t. This is the time where you should reverse engineer the work. Learn how they did it, how they solved certain problems. You should do so, not to replicate the piece, but to make it your own. Mix it with what you already know or give it a new twist; do something even better. That is how you should pay back.
The community, platform (Flash) would grow from this. People would start decompiling your work and even better pieces would be created. In the end, we would all win from this. Better creations means more confidence in the platform, more money invested into it (Adobe, web agencies) and more jobs.
If you think individually, you’ll only see the bad sides of decompiling, but if you open your mind and have a broader view, you’ll understand the benefits.
From previous posts you know that I am participating in the Flex SEO contest. I got my page pretty high on Google, but it still doesn’t seem to be finding my content. There are still a lot of unknown about this new SEO technology that Adobe, Google and Yahoo worked on and I think that to make a Flex application that load the content dynamically is to go a bit too fast.
So with that in mind I made simpler swf files. I even made some using Flash to see what would get indexed and how. In each of my experiments I have included a unique search expression basically formed from Fleximagically Searchable plus another word. If you search Google with that expression and one of my experiment shows up, it means Google indexed the content. Here are my experiments:
We don’t even know what type of swf is or is not indexed by Google so I sat down down and I made the simplest ones. Since Flex is pretty complex, I made some files using Flash.
The first one is only a static textfield right on the timeline. we know Google used to index those files, let’s see how it does it.
The second one is still in Flash using a prefilled dynamic textfield.
The third one is using a dynamic textfield again filled using ActionScript.
The fourth one is using a static textfield added to the stage using ActionScript.
Since we don’t know if Flex files get indexed at all, I made three simple experiments using basic components: TextArea, Label, Text. In those experiments the content is filled using the text attribute in the MXML file.
Flex file using TextArea.
Flex file using Label.
Flex file using Text.
Now let’s wait for Google to crawl these pages and then we will be able to better understand how this all works.
I have been thinking lately about what impacts will Silverlight have on me as a Flash Programmer. I came to the conclusion that it wasn’t really threatening. It could have been threatening in the sense that it could have made Flash obsolete and make me loose future jobs at the same time. But the thing is, Flash is such a good technology, it’s been around for a long time, the community supporting it is amazing and Adobe has big plan for it, Silverlight would have to be packed with a lot of feature in order to shake Flash’s position in the market. I don’t think it has just that.
It’s true that videos in Silverlight look good, but now with the moviestar release of the Flash Player, I don’t think one is better than the other on that characteristic. It’s nice for programmers who know .net, they can just jump right in and start programming Silverlight applications (maybe with a small learning curve). Good for them, .net programmers are already in demand, now they are going to be even more in demand, their salary is going to increase, so does the cost of building a Silverlight application.
One of the thing that Flash as always suffered was the penetration rate of the Flash Player, as a proof, website using flash 9 are now starting to emerge even if its been more than 6 month since it’s been release. Silverlight will suffer even more as people are not willing to download anything anymore. Flash as the chance to be adopted by huge website like Youtube and Facebook and has been around for way longer, people trust the Flash brand.
A big advantage Flash has over Silverlight is all the documentation lying around the web. If you want to know how to do something in Flash, just Google it, it’s that easy. Also open source projects like papervision3d and Tweener are just amazing.
For all these reasons, I don’t think Flash programmers have to be afraid for their jobs because of Silverlight and that for at least five years. I actually think Silverlight is a good thing; a little competition never hurt anyone, Adobe will have to keep improving Flash which is very good for us.