Frf app for android.

[QCCowboy]

Originally Posted by ependydad

The iPhone version, you pull down to refresh.

To know if you have new or old - the new iPhone one is primarily RED.

I'm thinking they tried to port this app from an iOS app to Android, either that or they are using a platform that attempt to allow it to run on both. Either way, they need to go back to the developers and make some changes.

[ependydad]

Originally Posted by QCCowboy

I'm thinking they tried to port this app from an iOS app to Android, either that or they are using a platform that attempt to allow it to run on both. Either way, they need to go back to the developers and make some changes.

My guess it's the latter - there are HTML5 platforms that let you write once and compile for each individual platform (called Cordova for the geeks out there ). I'm not sure, of course.

[QCCowboy]

Originally Posted by ependydad

My guess it's the latter - there are HTML5 platforms that let you write once and compile for each individual platform (called Cordova for the geeks out there ). I'm not sure, of course.

Yeah, it is too common for people to use app wrappers to get their apps deployed and deployed quickly. Unfortunately it has become about speed and cost and people don't put the effort necessary on User Experience that they need to.

[ependydad]

Originally Posted by QCCowboy

Yeah, it is too common for people to use app wrappers to get their apps deployed and deployed quickly. Unfortunately it has become about speed and cost and people don't put the effort necessary on User Experience that they need to.

I'm not sure that's it's a lazy thing (my words, not yours). The problem with mobile apps is that there are so few dedicated professionals in it. You have a hundred times the web developers (like me) than you have dedicated mobile guys and gals. So, if you can use something that is 90% web developer and 10% specialized needs - it just makes sense.

I actually helped prototype an app that used it. Pretty slick technology. It was able to give us an easily consistent interface across platforms (one of our requirements). And allowed us to consolidate code bases meaning bug fixes only had to be made once, etc.

There's actually little that I completely dislike about the new app (but again, there appears to be iPhone vs. Android differences). There are some differences that I have to get used to. But, hey- so it is.

[bikendan]

so far, i see no reason to update my version.

[WBrian]

Does anyone have the API file for the droid app? I have a Blackberry, but can install droid apps on it... Pm me for an email address...
Thanks!
Brian

[QCCowboy]

Originally Posted by ependydad

I'm not sure that's it's a lazy thing (my words, not yours). The problem with mobile apps is that there are so few dedicated professionals in it. You have a hundred times the web developers (like me) than you have dedicated mobile guys and gals. So, if you can use something that is 90% web developer and 10% specialized needs - it just makes sense.

I actually helped prototype an app that used it. Pretty slick technology. It was able to give us an easily consistent interface across platforms (one of our requirements). And allowed us to consolidate code bases meaning bug fixes only had to be made once, etc.

There's actually little that I completely dislike about the new app (but again, there appears to be iPhone vs. Android differences). There are some differences that I have to get used to. But, hey- so it is.

Understand your point here, and by no means do I disagree. My point is that often when using these wrappers there are certain things that still need to be modified to provide a solid UE. The way the wrapper works may not be optimal "out of the box". That might be why the refresh for the new app is subpar in my opinion and the menu system needs work when on Android. I can definitely feel the attempt to leverage an iOS app here.

These UE items can be neglected in attempt to get an app to market.

[ependydad]

Originally Posted by QCCowboy

Understand your point here, and by no means do I disagree. My point is that often when using these wrappers there are certain things that still need to be modified to provide a solid UE. The way the wrapper works may not be optimal "out of the box". That might be why the refresh for the new app is subpar in my opinion and the menu system needs work when on Android. I can definitely feel the attempt to leverage an iOS app here.

These UE items can be neglected in attempt to get an app to market.

Ahh, I hear you. If they did use PhoneGap (sorry, I called it an old name before), the wrapper enforces very little and it's up to the HTML developer to be responsible for the UE itself. It's literally just a compiler helper to get the app to each platform. (From the little that I used it, of course.)

No clue how they actually built it, though.

[ependydad]

Interestingly, based on the description in my iOS app update, it refers to "Tapatalk BYO".