(Locked) Compatible With iOS 5.0 & 5.1 Now Added For Mobile

Hey everyone! Hope you are all well

Some of you have been asking for this so I wanted to pop in to let you know we have just added compatible with iOS 5.0 & 5.1 for use with mobile items. Please update your files accordingly.


Let me know if you have any questions.

It would be cool if we could get the browsers updated on CodeCanyon. Instead of Firefox 3/4 and Safari 4/5, maybe we could just have a single “Firefox” and “Safari”. And then a single “IOS” and “Android” would also be nice as lots of customers are now interested in this compatibility.

CodingJack said
It would be cool if we could get the browsers updated on CodeCanyon. Instead of Firefox 3/4 and Safari 4/5, maybe we could just have a single “Firefox” and “Safari”. And then a single “IOS” and “Android” would also be nice as lots of customers are now interested in this compatibility.

Hi Coding Jack! Thanks for the suggestion. My guess is we would run into issues with this since authors would need to keep their items updated to the latest version at all times in order to avoid problems for buyers.

JoshuaSprague said

CodingJack said
It would be cool if we could get the browsers updated on CodeCanyon. Instead of Firefox 3/4 and Safari 4/5, maybe we could just have a single “Firefox” and “Safari”. And then a single “IOS” and “Android” would also be nice as lots of customers are now interested in this compatibility.

Hi Coding Jack! Thanks for the suggestion. My guess is we would run into issues with this since authors would need to keep their items updated to the latest version at all times in order to avoid problems for buyers.

Thanks for responding Josh

This is why I think getting rid of versions is a good idea and simply sticking with platforms only. For example, right not, saying that a file is compatible with Firefox 3 and 4 isn’t very helpful, as I just updated to 14 this morning.

I see your point about authors needing to make sure their plugins work with new versions, but I think the likelihood of a problem occurring is small (at least for the JavaScript category). But if a problem does occur, it could be a positive thing as the author could just be asked to update their product, or remove the platform listing their product no longer supports. Either way it’s a win win for the customer.

CodingJack said

JoshuaSprague said

CodingJack said
It would be cool if we could get the browsers updated on CodeCanyon. Instead of Firefox 3/4 and Safari 4/5, maybe we could just have a single “Firefox” and “Safari”. And then a single “IOS” and “Android” would also be nice as lots of customers are now interested in this compatibility.

Hi Coding Jack! Thanks for the suggestion. My guess is we would run into issues with this since authors would need to keep their items updated to the latest version at all times in order to avoid problems for buyers.

Thanks for responding Josh

This is why I think getting rid of versions is a good idea and simply sticking with platforms only. For example, right not, saying that a file is compatible with Firefox 3 and 4 isn’t very helpful, as I just updated to 14 this morning.

I see your point about authors needing to make sure their plugins work with new versions, but I think the likelihood of a problem occurring is small (at least for the JavaScript category). But if a problem does occur, it could be a positive thing as the author could just be asked to update their product, or remove the platform listing their product no longer supports. Either way it’s a win win for the customer.

Those are valid points, let me bring this up with the team and get back to you on this one. Thanks again for your input!

mistake…sorry.

CodingJack said

JoshuaSprague said

CodingJack said
It would be cool if we could get the browsers updated on CodeCanyon. Instead of Firefox 3/4 and Safari 4/5, maybe we could just have a single “Firefox” and “Safari”. And then a single “IOS” and “Android” would also be nice as lots of customers are now interested in this compatibility.

Hi Coding Jack! Thanks for the suggestion. My guess is we would run into issues with this since authors would need to keep their items updated to the latest version at all times in order to avoid problems for buyers.

Thanks for responding Josh

This is why I think getting rid of versions is a good idea and simply sticking with platforms only. For example, right not, saying that a file is compatible with Firefox 3 and 4 isn’t very helpful, as I just updated to 14 this morning.

I see your point about authors needing to make sure their plugins work with new versions, but I think the likelihood of a problem occurring is small (at least for the JavaScript category). But if a problem does occur, it could be a positive thing as the author could just be asked to update their product, or remove the platform listing their product no longer supports. Either way it’s a win win for the customer.

+1 for that!

totally agree with the confusion with some browsers included etc because Chrome for example auto updates and FF is in version 14 now…

This is such a pointless feature because software moves so fast (well, Apple software doesn’t) and if you’re not going to update the browser list or other software, it kinda causes more confusion then its worth.

Either keep an update to date list of software and versions of drop the version numbers. That’s the way I see it….

....Oddly enough, I asked for this months ago, and when I put the thread up, it totally went ignored…:(

until it’s implemented I think the best bet is to include it within your description and update it yourself… not as nice but i’m sure they’ll eventually roll something out…

also, how do you test in all the dot releases, do you guys have thousands of browser versions installed because they usually force you to upgrade the one you have installed?