We don’t trust paypal at all and, since Envato has no feature to split the income, we use payoneer to share our earnings because it has free card-to-card transfer up to 5k usd per month.
This allows us to avoid any % based fee but one of us must get whole amount first, that was my answer to your original question and why the trust matter was pulled in the discussion.
UndergroundMovie saidTo realize a great (or poor) item would just help you decide whether your partnership is worth the effort or not. You gotta trust each other regardless or else working together will be an issue.
If our work will be great, then we will trust each other for sure
My advice would be to just focus on the project and assume your team mate won’t try to back-stab you at the first chance. Even with signed paper and every precaution you can think of right now, if bad s**t is bound to happen, it will nonetheless.
We do split 50/50, one of us gets full amount and sends the other one his share via payo c2c transfer.
Mutual trust is a must for a long term and successful collaboration here. If you feel the need to sign a paper and/or collecting evidences that could be eventually used against your team mate, you’re doing it wrong unless it’s a one time project.
billyf saidThe api change is massive, happened after theme release and would require complete rewrite of the code (no to mention the buyer api key). Most buyers would understand that the change is not under our control and the fact they bought a theme and not a twitter plugin.
But for those who have already purchased the themes, wouldn’t they complain if the feature is suddenly removed? After all, when they purchased it, ‘probably’ they bought it because there’s such feature (I know it’s very unlikely, but who says your buyer can’t use that reason?)
that plugin uses API 1.0 and will soon stop working.
New api is madness … oauth required even to just fetch tweets and api calls per hours are limited so data must be stored server side (a pure js solution is no longer an option)
Not to mention buyers will be obliged to create their own api keys before being able to use the widget and guess who they are going to ask help with …..
Not worth the effort, at least for us, so we just removed the twitter widget from our standard list of features.
twitter did the same thing, you can no longer fetch latest tweets without oauth/apikey and also required to store the content (because the per hour fetch limit restrictions) so a js only solution is out of question.
item support is already hard enough so we decided to just remove all social related custom widgets from our themes and buyers will have to rely on 3rd party plugins for this kind of features.
Android SDK emulator is nowhere comparable to the real device so it’s not really an option. We do test on android 4.x phone and tablet and ensure everything works as expected (layout/functions)
However, most of the times there’s not much you can do to optimize a plugin/template/theme for this platform when it comes to transition/scroll smoothness and touch events handling.
Truth is (omg i hate myself for saying this), apple mobile safari is still way ahead its competitor stock browser so you just end up optimizing for ios and to accept compromises on android.