topic Re: Flex VS Javascript APIs in ArcGIS Viewer for Flex Questions

Flex VS Javascript APIs

GuillaumeTurcotte — Mon, 18 Jun 2012 15:43:58 GMT

I started building web map applications using the ESRI APIs available from the company. Being that I was familiar with Javascript, I started using those APIs, but I am having a very hard time working with them and customizing it to my needs. I took a look at the FLEX APIs and they way more seamless and easy.
So now, I'm at a cross road and looking for a little advice. Being that I have a little bit of a background using Javascript, should I keep it up and try and use those APIs and take the time and learn it or would this be a good time to chuck Javascript in favor of learning to use Flex? Has anyone made that switch? Any advice would be greatly appreciated. Thanks so much.

Re: Flex VS Javascript APIs

RicoSantiago — Thu, 26 Jul 2012 12:27:17 GMT

Hi! I too am at that crossroads. I'm a bit hesitant about jumping into Flex considering Adobe is no longer supporting Flash for mobile devices. Considering mobile is becoming such a big part of the tech-ecosystem (not to mention, organizations in my field are moving toward or, at the very least incorporating, mobile platforms as part of their workflow), I'm a bit concerned investing in the time to learn and develop Flex-based apps is a bit of a "dead end". Any other thoughts on this?

Re: Flex VS Javascript APIs

JordanParfitt — Thu, 26 Jul 2012 18:46:34 GMT

I started with the JavaScript API originally. I had no problem with it, well documented and easy to learn. Mostly just worked in Notepad++ and Firebug. A little later when the Flex API came out everyone started asking for it, so I started using that. Again I thought it was pretty easy to learn. It wasn't until the iPad came out that I had to go back to JavaScript. No one was trying to use a huge viewer on their phone, but the table makes it more practical.

At the moment I split 50/50 between JavaScript and Flex. I have no problem going back and forth, and I will say the Viewer for Flex makes rapid application development a breeze. I am also less worried about cross testing in different browsers (but differences do come up from time to time). That being said when a client gives me the choice I use the JavaScript API, it's just the way the industry is going and the skills you develop will help if you ever want to work with more JavaScript libraries (jQuery, Dojo, Leaflet, Google, Openlayer, etc).

Re: Flex VS Javascript APIs

TateM — Fri, 04 Oct 2013 01:19:38 GMT

I think the benefit is with JavaScript API, just because JavaScript is embedded in HTLM5. For future use especially in moving towards Mobile, HTM5 is the way to go. So you don't have to worry about any plug ins like Flash for Flex, silverlight etcs. Correct me if I'm wrong, but I believe Adobe will discontinued support flash when it comes to Mobile, and fully support Flash in HTML5. So it makes sense to go with JavaScript API, I think! Although I think Flex is really "sexy" looking just out of the box, and in term of cosmetically/esthetically. I really haven't seen JavaScript being that good looking. But then again I haven't really use JavaScript all that much, so I could be wrong. What do you guys think?