question regarding the Autoxxxxxx collection of plugins

[den...@gmail.com]

I have most of your Auto-plugins.
APPS,cast,input,remote,location,voice..etc.

I've used parts of each to prototype an apk I've been working on for someone.

When I compile my TASKER project it works, but when I try to put the apk on another phone, it prompts to download (and purchase i assume?) all the Autoxxxx plugins.

Is that how it works?

Thanks,
Dennis

[João Dias]

Yes, that's how it works :)

--
You received this message because you are subscribed to the Google Groups "joaomgcd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joaomgcd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[den...@gmail.com]

well,
that's a game changer
:(

Dennis

[João Dias]

Sorry!

Dennis

[den...@gmail.com]

Disappointed.

Are there any workarounds for this?
Did I miss anything on the play store information that would have alerted me to this limitation?

TASKER is a very powerful tool and more than adequate for *very serious* rapid prototyping.
I don't mind paying for plugins for that purpose.

I thought plugins were "tools" for *me* to build stuff.
If it's not, then this is a paradigm shift from the "old" way of doing things.

After a project is compiled to an apk, the end user should not be required to also repurchase the "tools" again.

That's like asking an end user to purchase Microsoft Office just to view a "doc" file.
That's like asking an end user to purchase Adobe just to view a "PDF" file.
That's like asking an end user to purchase AutoCad just to open a file that's only going to be used for his 3D printer.
That's like..etc etc..well, you know

In that sense, the Autoxxxx plugins are not really "tools". They are more like hard to find raw materials that must be repurchased over and over.

I understand that's good for your bottom line but that regulates plugins and, ipso facto TASKER, to "hobby" tools.
They (it) could be so much more.

There should be some way to purchase a "developer edition" of your plugins so apks could be truly self-contained?
I dont think I'm the only one who would pay a premium for that.
Time IS money.

Lacking that, I remain,
Disappointed.

Dennis

[João Dias]

hi again.

Sorry, but Tasker is an app that's developed by one developer (not me), and my plugins are separate apps.

You're asking Tasker's developer to create an APK that contains any third party app that's used in the exported project inside it.

I don't even know if it's technically possible to do that, but I really doubt it.

In any case, I really think you should talk to Tasker's developer about this, since he is the one that built the app-building tool.

Maybe he can shed some more light on the issue

Sorry to disappoint, wish I could help

João

Dennis

[RudeboyX]

I'm pretty sure it advises somewhere in the app export process in Tasker that the target device will also need to install any 3rd party plugins you have used in your exported app.

Also,if the plugins were included in the exported app, you could then sell someone elses plugin for personal profit.

"After a project is compiled to an apk, the end user should  not be required to also repurchase the "tools" again."

"In that sense, the Autoxxxx plugins are not really "tools". They are more like hard to find raw materials that must be repurchased over and over."

Once you have purchased the plugin, you are free to use it yourself forever without limit. You will never have to purchase it over and over and so is nothing like a raw material.

Now..... if somebody else wants to benefit from a plugin, they must pay for it like everyone else (only once though).

This is how it works and I doubt Takser will ever include 3rd party plugins in exported apps, Even if it was possible, it's unlikely that the plugin developers would be happy about people spreading there plugins around for free and so would no doubt lead to some legality issues.

Regards

Scott