[Panjo]

Originally Posted by markoroots

The problem is that no one want have an open interface (API) of a third part site on the own forum.
The plugin should work alone on our forum and just the name of the plugin (Panjo) is an advertising of Panjo site, I think that this is just enough to advertise Panjo.
If our clients must make a registration on panjo site to have an account on our forum is really ridiculous. We don't want programs in Iframe on our site.
I really don't know why vb put this iframe plugin on our site by default and after say on them official site also that them don't know how the plugin work. Also this is ridiculous. Don't you see that no one use this plugin??? Do you ask yourself the why??

In the last 30 days (December 2015), 600k individuals used the plugin across ~100 vBulletin partner marketplaces. They created thousands of listings. Buyers purchased $4M USD in products, parts, and accessories.

Why in the world is Panjo architected the way it is?! Panjo has been powering marketplaces for vBulletin partner communities for nearly five years. In that time we have learned a lot about the services and benefits buyers and sellers value most. In order to provide the most secure and cost effective (Panjo is free for communities) product, Panjo has arrived at an architecture as follows:

1) Partner gets a dedicated, customized community marketplace on Panjo.com
2) When a seller connects a Panjo account to a participating forum, the seller's listings generate thread posts on that forum.
3) Panjo synchronizes the data between the community marketplace and the forum.

Why take that approach?

a) mobile users: Panjo develops each screen in three versions: desktop, tablet, and mobile. When Panjo was operating a more feature-rich iFrame, it was expensive and buggy to try to deploy an exception buyer and seller experience in a responsive design.
b) work flow: Let's say you are a seller and your item just sold. When you get an email notification about the sale, you want to accept or reject the payment depending on a number of factors (location of buyer, availability of item, familiarity with buyer). Panjo can send transactional emails to buyers and sellers that provide links that auto log-in the user to reduce friction and steps.
c) QA (quality assurance): Let's say Panjo is once again shipping new features (like we do every Tuesday). It is near impossible to insure the quality of those features when they are deployed to 100s of iFrames inside 100s of versions of vBulletin that could be using 100s of permutations of plugins that could be hosted on 100s of different server environments. We hated deploying a feature that might be buggy for a set of users. It was near impossible to QA a feature when the environment it would live in existed in 100s of permutations.
d) There are lots of product, security, user benefit, and community benefit reasons Panjo exists in the architecture it does.

We are proud of our legacy and on going progress constantly improving an exceptional peer-to-peer marketplace experience for our members.

Here are what some members have said recently:

"Great service, where honest professional transactions can occur. Listing is user friendly, even for us older folks. Thanks"
"No fee, easy setup, item sold very quickly. Excellent UI and overall positive experience."
"The items are of good quality and the members seem to be polite"
"It works and it's painless and easy for both parties. It's nice to be able to just get notification that you have payment there's a provision to put tracking info and there's record of conversations great place to conduct business"