New Marketplace sneak peak

[Scott_Harrison]

As a lot of users are aware the marketplace will be shutting down after May 1 of this year. You will still be able to download the current versions of the plugins once the marketplace shuts down. But in order to continue to update and support the development of new plugins a new marketplace need to be build.

I am happy to announce that work on a new marketplace has began and will be available as a beta on March 27. While the current plan is port over all existing plugin that I made, new or other plugin/asset markers be able to host their content as well (feel free to dm me ). 

Here is a sneak peak (note: expect designs and layouts to change )

[pixec]

How would a new plugin developer sign up and use this? What costs would there be and would this be linked with Corona or is this connected with richard11 or something?

[richard11]

Ah… I do wish you’d posted this sooner! Seems we have some competition on our hands now, ha.

[anon63346430]

Communication is a wonderful thing sometimes!

[Scott_Harrison]

@pixec

How would a new plugin developer sign up and use this? What costs would there be and would this be linked with Corona, or is this connected with richard11 or something?

The new marketplace is still a WIP. It would be a similar process corona marketplace. You would submit your plugin, it would be tested, and it would be then be submitted and hosted on my severs which would either sync with github or just would allow you drag and drop your new version directly on my website.

I am assuming by what cost you mean to developers? I would probably be 10-30%. I don’t have specifics, I am hoping the beta with my own plugins and will give me a better idea of typical usage.

This is being developed as an independent project.

[Scott_Harrison]

Here is a preview of the product page (all data be dynamically similar corona marketplace)

[Scott_Harrison]

Just wanted to give a small update. I still plan on doing a public beta on March 27. This beta be a handful of plugins I made. Hoping to extend this to 3rd parties in the near future.

Just completed my first test successfully authenticating user and downloading plugin with corona simulator for ios and android.

[Scott_Harrison]

Here is a small preview
https://youtu.be/0vWGWP1h6M0

[pixec]

Isnt it super risky to pass parameters in url or is my info wrong? Doesnt that also mean if you develop with someone else, they get your login details to the entire store?

[Scott_Harrison]

@pixec

Isnt it super risky to pass parameters in url or is my info wrong? Doesnt that also mean if you develop with someone else, they get your login details to the entire store?

The idea is to not want to share so individual account with others. Very similar to how Coronas marketplace work. You don’t share your corona password with others. I don’t want 100 people using same url. I can as monitor downloads for individual users so for example if 10 people are downloading at the around the same time I will reach out with a warning to change their password. Obviously if it is for a business you should reach out for a group discount.

I looking into passing password info in the header of url using basic authentication which may be more secure which would be you would pass in email and password into the front of the url. Just an FYI, no credit card or address info will be stored on your account. While this may be a pain to type out info, I don’t feel comfortable storing this info (plus most browsers auto fill will work)

[richard11]

Kudos for progressing quickly with this. I’ll be honest, life’s getting in the way at this end and I’m still a fair way off showing anything of ours.

Ref your URLs - you could create a unique hash for each account and use that in the URL rather than the account login. Same mapping, but would allow for teams to work on the same project without seeing account logins.

Ref storing card details - you’re absolutely right to feel uncomfortable with that. My company specialises in e-commerce and we’d never do this either. I talk clients out of it on a weekly basis - far too much of a data protection headache.

[anon63346430]

@Scott\_Harrison

I looking into passing password info in the header of url using basic authentication which may be more secure which would be you would pass in email and password into the front of the url. Just an FYI, no credit card or address info will be stored on your account. While this may be a pain to type out info, I don’t feel comfortable storing this info (plus most browsers auto fill will work)

Having worked under PCI regulations this is a massive no!  You have to use a public key/private key solution.

[Scott_Harrison]

^Thanks for the feedback just implemented a system like this

https://scotth.tech/marketplacePlugins?ID=q7w5is&plugin=FirebaseAnalytics_scotth-tech&type=iOS (note the url is deactivated)

You can also refresh the Account ID anytime in setting (which kill out all links using the that ID) and it will only give you access to a plugin list for that account not the account itself.

[Scott_Harrison]

While everything is looking good so far going to take the weekend to try to add a couple more plugins and test a couple of things to be ready for a beta launch on Monday (March 30).

[Scott_Harrison]

Just wanted to give a small update. I still plan on doing a public beta on March 27. This beta be a handful of plugins I made. Hoping to extend this to 3rd parties in the near future.

Just completed my first test successfully authenticating user and downloading plugin with corona simulator for ios and android.

[Scott_Harrison]

Here is a small preview
https://youtu.be/0vWGWP1h6M0

[pixec]

Isnt it super risky to pass parameters in url or is my info wrong? Doesnt that also mean if you develop with someone else, they get your login details to the entire store?

[Scott_Harrison]

@pixec

Isnt it super risky to pass parameters in url or is my info wrong? Doesnt that also mean if you develop with someone else, they get your login details to the entire store?

The idea is to not want to share so individual account with others. Very similar to how Coronas marketplace work. You don’t share your corona password with others. I don’t want 100 people using same url. I can as monitor downloads for individual users so for example if 10 people are downloading at the around the same time I will reach out with a warning to change their password. Obviously if it is for a business you should reach out for a group discount.

I looking into passing password info in the header of url using basic authentication which may be more secure which would be you would pass in email and password into the front of the url. Just an FYI, no credit card or address info will be stored on your account. While this may be a pain to type out info, I don’t feel comfortable storing this info (plus most browsers auto fill will work)

[richard11]

Kudos for progressing quickly with this. I’ll be honest, life’s getting in the way at this end and I’m still a fair way off showing anything of ours.

Ref your URLs - you could create a unique hash for each account and use that in the URL rather than the account login. Same mapping, but would allow for teams to work on the same project without seeing account logins.

Ref storing card details - you’re absolutely right to feel uncomfortable with that. My company specialises in e-commerce and we’d never do this either. I talk clients out of it on a weekly basis - far too much of a data protection headache.

[anon63346430]

@Scott\_Harrison

I looking into passing password info in the header of url using basic authentication which may be more secure which would be you would pass in email and password into the front of the url. Just an FYI, no credit card or address info will be stored on your account. While this may be a pain to type out info, I don’t feel comfortable storing this info (plus most browsers auto fill will work)

Having worked under PCI regulations this is a massive no!  You have to use a public key/private key solution.