current mobile suite?
Collapse
X
-
-
anders | vbulletin team | check out the new vbulletin facebook app
Proudly vBulletin'ing since 2001
Please be my friend! http://www.twitter.com/inetskunkworks
vBulletin Performance Articles: Click here to readComment
-
Thank you for this update. Will we also be seeing more updates more frequently after this next one? Does this mean the staffing/resourcing issue has been resolved? Thank you!Comment
-
I'm sorry to say but the fact that the mobile license expires every year, it doesn't seem to be in vBulletin's interest to release quickly.My Sites :Comment
-
I'm sorry to say but the fact that the mobile license expires every year, it doesn't seem to be in vBulletin's interest to release quickly.Comment
-
This isn't down to desire to bring in more money by not updating it but by resource issues as previously stated. I'm sure you've all seen that mobile developers have left...Comment
-
Hello Trevor, I actually didn't notice that! Hahaha Are they going to be replaced by a whole new group of Mobile Developers? Thank you for the updates!Comment
-
To pacify the forum and those who are using the mobile product, I recommend vbulletin extend the current license period for those who have purchased the product. We, the users, are not responsible for vbulletin's resource problems.
I purchased the mobile suite in May 2011. My license renews in May 2012. It's November 2011, 6 months after purchase, and I've seen 1 (one) update to the android product, another update to the form generator vbulletin uses to configure the app.
The current updates/upgrades for Android have not been made available due to "resource problems" for several months. But again, those resource problems are not the responsibility of the users who purchase the mobile product.
In the name of positive PR and good will, please pass forward that those who purchased the mobile license have their license extended for a few months because of the resource problems, or the license period does not run until vbulletin can fix the problem and get the necessary employees to support the mobile product.
I write this with all due respect and thank you for your consideration.👍 1Comment
-
I think this has been the opinion of all, even those with just vB forum classic, for a long time now, TBH. We bought a product and are now helping to finish it via the community. It's still not done even with all this community effort to date. Why not? And if it is a resource issue, that's not our problem thats a management problem. Either way, you have our money, the clock is ticking and the version keeps increasing toward the next full version and more money. More money that people are already choking on.
You don't make due with the Developers you have, you go out and hire more to get the job done. This is not an open source project. (although it plays one online here every day more and more it seems.)Comment
-
Trevor and Support,
To pacify the forum and those who are using the mobile product, I recommend vbulletin extend the current license period for those who have purchased the product. We, the users, are not responsible for vbulletin's resource problems.
I purchased the mobile suite in May 2011. My license renews in May 2012. It's November 2011, 6 months after purchase, and I've seen 1 (one) update to the android product, another update to the form generator vbulletin uses to configure the app.
The current updates/upgrades for Android have not been made available due to "resource problems" for several months. But again, those resource problems are not the responsibility of the users who purchase the mobile product.
In the name of positive PR and good will, please pass forward that those who purchased the mobile license have their license extended for a few months because of the resource problems, or the license period does not run until vbulletin can fix the problem and get the necessary employees to support the mobile product.
I write this with all due respect and thank you for your consideration.Comment
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment