Turnkey Mobile Apps for XenForo with Addon/Theme Support, Android & iPhone [Deleted]

I am trying to setup the free demo. I got it figured out, but when I check on the status of my app it just keeps saying, "Waiting For Addon Install".

The add-on is indeed installed though, and I'm 100% certain it was done correctly. Does it take some time for this to update on your end?

And once it detects the add-on is installed, do I have to wait for the app to show up in the app store, or do you send me a trial version to test out? I'm confused about that part.
 
I am trying to setup the free demo. I got it figured out, but when I check on the status of my app it just keeps saying, "Waiting For Addon Install".

The add-on is indeed installed though, and I'm 100% certain it was done correctly. Does it take some time for this to update on your end?

And once it detects the add-on is installed, do I have to wait for the app to show up in the app store, or do you send me a trial version to test out? I'm confused about that part.
@PumpinIron Apologies for the issue; it's been fixed, but we had to reject the app because we know the store review teams will reject it on copyright grounds (specifically, the name of the forum has a trademarked vehicle model name).

Does this allow for ads?
Yes, all ad code and plugins work inside the app.
 
@PumpinIron Apologies for the issue; it's been fixed, but we had to reject the app because we know the store review teams will reject it on copyright grounds (specifically, the name of the forum has a trademarked vehicle model name)..

Ahhh, so there's no real way to get the app working with my forum since it uses a trademarked vehicle name?
 
Ahhh, so there's no real way to get the app working with my forum since it uses a trademarked vehicle name?
If you get a signed document from Jeep granting permission to use their trademark in the site/app's name/domain, then the app stores would approve it.
 
FEATURE REQUEST:
(ACP option) App Usage bound to membership level.

Let's say I have basic, advanced, premium membership levels/groups and I only want the premium (paid) group be able to use the app. It would be great to have an ACP option to "bound app usage to user group" (with selectable user groups) and deny app usage to the rest. Everybody else (including unregistered/guest user groups) receive a notification: "You don't have permission to use the app – please upgrade your membership level" (phrased of course).

That would help admins to redeem the costs of the app easily when distributing the app via private (non-shop) channels.

@vbresults it could have been missed here.
 
You could do that on the xenforo side fairly easily now with permissions and wouldn't need to be app enabled.
I am not quite sure how, but am open for any hints and directions. The XF side has an add-on part and I think template mods. One could wrap those templates into a conditional that asks for the right user level and then spits out a message. But that sounds rather raw than elegant.
 
Do you offer any sort of monthly payment option?
We did give it a fair shot and it didn't crunch out, so there is not and we have no plans to restore it. Even if the pricing was divided into a lump sum on one side and the support costs spread over monthly, we've done enough testing to know it wouldn't work.

Enough would sign up and try to game it by cancelling the subscription and later demand support they chose to not pay for, then spin it differently in complaints. With the data gathered up to this point, the only situation where monthly could possibly (not necessarily) work is with huge distribution.

Aside from the 1st mover everyone knows of, the only other possible way is official xF distribution.

@Freelancer We got rid of the DIY plan (where you do the publishing work yourself) first because almost nobody used it since we made the full and proper disclosures about what's involved in publishing an app yourself. We didn't want it to end up like the vBulletin Mobile Suite.

It was also possible for the support costs of DIY to exceed TMA even though DIY cost $100 less. Mathematically it did not work. With DIY gone, if you want the apps published under your store account, you can use the Enterprise plan but like Turn-key that's app-store only and we do all the work.

Under consideration is a more exclusive option that caters to advanced admins, allowing them to have an off-grid* app. We floated this when the app was known as Native+ then decided against it, but we'll look at that again.

Off-grid:
  • Run their own push server
  • Publish their own app
  • Implicitly, that means they use their own app store account
There are advanced admins (and companies with tech staff) interested in this option, independent of those that just want a lower price. That said, unless one already had a Mac and app store account, Turn-key are Enterprise are both less expensive (don't have to buy a Mac) and more easy to manage..
 
Last edited:
FEATURE REQUEST:
(ACP option) App Usage bound to membership level.

Let's say I have basic, advanced, premium membership levels/groups and I only want the premium (paid) group be able to use the app. It would be great to have an ACP option to "bound app usage to user group" (with selectable user groups) and deny app usage to the rest. Everybody else (including unregistered/guest user groups) receive a notification: "You don't have permission to use the app – please upgrade your membership level" (phrased of course).

That would help admins to redeem the costs of the app easily when distributing the app via private (non-shop) channels.
I've asked for this is the past [1, 2]. It's not something they seem desirable or wanting to develop, even suggesting it's not really possible. It's encouraging that others want it too.
 
I've asked for this is the past [1, 2]. It's not something they seem desirable or wanting to develop, even suggesting it's not really possible. It's encouraging that others want it too.
It's not a matter of what is desirable at this point.
That qualifies as an in-app purchase (benefit is received in-app only) and in such cases Apple/Google force you to use their payment system. They do this so that they can always take a 30% cut (their golden goose), if you don't like it they don't let you publish.

If you try to circumvent it, they eventually find out and ban you. Standard user upgrades don't count as in-app purchases because the benefits aren't app-only.
Apple says no circumventing their in-app purchases (meaning to links or text directing to account upgrades in-app). They are clamping down hard on this recently and we even had to disable account upgrade links from showing in-app in 2.2.

If anyone tries to implement this in any form, it will not make it past Apple's gatekeepers.
 
@vbresults I installed the new add-on and the Two Two Style – as in the install instructions. However, I could not find how to associate the style to the app as it was possible in the past options. Also, I was wondering about the style not selectable in the "style chooser" in the footer but in the account "preferences"... (which I wonder if it's intentional or a bug). Furthermore it does looks like a slightly modified XF "Default" style, is that correct?
 
@vbresults I installed the new add-on and the Two Two Style – as in the install instructions. However, I could not find how to associate the style to the app as it was possible in the past options. Also, I was wondering about the style not selectable in the "style chooser" in the footer but in the account "preferences"... (which I wonder if it's intentional or a bug). Furthermore it does looks like a slightly modified XF "Default" style, is that correct?
Just patched the add-on minutes ago and if you re-download it and overwrite the existing php files, it will fix the selection issue bug; the way to associate the style to the app is by going to the "Turnkey Mobile Apps" style properties and checking "App Style".

Note this will make the skin you checked unavailable outside of the app. While this is ok for Twenty Two since it's app-only anyway, for others you need to make a child style & check the box there instead of in the original.

Twenty Two does not look like a slightly modified XF default style, it is a custom skin -- you might be thinking of the old generic in-app style we used to bundle with the app at certain points, which was discontinued some time ago.
 
re-download it and overwrite the existing php files, it will fix the selection issue bug

It did not change anything. I can not select Twenty Two in the style chooser (it does not appear there), I can only select it in the account preferences and it looks just like the default style.

If I got to the Style Properties I only see "App Style" and no names or any of my other styles (although selection of different styles is mentioned in the description under the checkmark)
Bildschirmfoto 2017-04-16 um 15.53.25.webp
If I check it on, the complete board goes into the Twenty Two style and I can not chose any other style then default or UIX (that I have installed beside three different other styles).
 
@Freelancer To make sure I understand right, there are six styles. Twenty Two, Default, UI.X, and three others. Which ones do you want available inside the app and which ones do you want available outside the app?
 
Back
Top Bottom