I am hosting a hackathon at my company and intending on making use of the Spotify WebAPI. I wanted to know what the preferred way of registering apps (does every attendee need a Spotify account or is there some work I can do ahead of the hackathon to have everything ready), as well as notify Spotify of a period of time they can expect a high volume of requests originating from my company's IP.
My planned approach is to have 1 premium account with multiple apps registered (1 per team). Is there a better way to do this?
Related
I need to implement a renewable subscriptions in my mobile application, with different plans, duration and prices (like Netflix is doing), that is valid on mobile but also in my desktop app.
I read many threads and I understood that the only way to know if the subscription is correctly renewed is to check it from the mobile app: this is a problem for me because if I bought a subscription in my mobile app and I stop using it, but I'm still using the desktop application, at the end of the subscription I will not know if the subscription was renewed (because the user never opened the mobile app) and so I'll block the user for log-in in the desktop app.
I also read that it's not possibile to use Stripe or Paypal to manage the payment in mobile app, because the store will block the application that is not using a proprietary purchase system to sell not-physical goods or services.
So, the question is: is there a way to make a recurring subscription and know if it's currently active or not and the total payed without open the mobile app? If not, how can I manage a recurring subscription both in mobile and desktop apps? May be I'll need to create an external web page using a webview and then use Stripe or Paypal?
Thanks.
Matteo
Font:
Renewalbe subscription on mobile
Implement Stripe in Xamarin
EDIT
Our purpose is to manage subscriptions on desktop application but give the mobile user the possibility to buy a plan also on mobile.
Is possible to use a web view or default mobile browser to redirect the user to desktop web page and buy from here, without have any problem when publish app on apple and play store.
I plan to use a 3rd party payment gateway for in-app purchases for an app distributed through the Google PlayStore. I'm aware of Google's policies regarding payments for in-app purchases (https://play.google.com/about/monetization-ads/payments/)
My content / service delivery model is as follows:
When a user pays for a plan he gets—
Certain features in the app
Certain features in our web portal, completely outside the app
Our deployment staff going and visiting the user's location and
providing training and setup services.
For some plans, we will be delivering a physical device to user's
locations (a POS machine to accept card payments)
Since my offerings are a combination of physical and digital goods and services provided within and outside the app, it does not clearly fall under the categories Google mentions in the link above.
My question is: Can I use a 3rd party payment gateway to accept payments within the app given my content / service delivery model?
Do I risk being blacklisted? Does Google give a time window to react by sending an email first before pulling apps down.
I know my question is similar to this one: Android In-app purchases and I'd like to get similar opinions on my planned content / service delivery model.
Kindle PlayStore app, distributed via Play Store also seems to be an example of an app using different payment method from Google's billing APIs
My company has different websites for different customers, each of them using instagram API to retrieve pictures from customer's instagram account.
I have tried to register different instagram clients but it has been rejected because 'We don't approve multiple submissions for the same company. Please consolidate all your integrations under a single client_id.'
How one would solve this problem ? An instagram client has its own website url, privacy policy url and redirect_url which obviously can't be shared between different websites.
It sounds like you are trying to get your client approved to "go live"... does it meet one of their only three acceptable use cases (since June 1st 2016)?
“My app allows people to login with Instagram and share their own
content”
“My product helps brands and advertisers understand, manage
their audience and media rights.”
“My product helps broadcasters and
publishers discover content, get digital rights to media, and share
media with proper attribution.”
If your use case doesn't fit their new agenda you will never get it approved to go live no matter how consolidated it is. Your only other option is to stay in Sandbox mode. First read about the limitations of Sandbox mode and if these are acceptable, then you don't have to worry about submission process at all. Just create multiple API clients and leave them in Sandbox mode forever. But if you're doing anything besides showing a few recent photos on your customer's sites, Sandbox mode probably won't cut it for you and you may be out of luck.
I'm just working on a Node.js project which uses Instagram API to boost up users likes/comments & follower numbers by focusing on user specific tags and automatically create organic bonds between users with liking and commenting. Or you can call this shortly as a Instagram bot.
However, the rate and user limits of the Instagram API made me curios about some stuff.
Firstly, the process for going live in Instagram looks so complex and toilsome so how the well-known Instagram BOTs (Archie, Instagress etc.) can made this ? Because I thought Instagram never accepted a usage for their API for this purpose and their Platform Policy is so strict that one can not hide their main purpose.
Secondly, even though app goes to live , the rate limit for endpoints used to publish (POST or DELETE) so limited that how these bots can work fluently without exceeding these limits even they have a lot of users ?
It would be best if anyone is experienced about Instagram API and the Instagram bots can answer there questions.
they develop it without official instagram API, they used private API that uses instagram mobile application. I developed instagram bot, I have it on my local server.
Some time ago, it was commonplace for smartphone apps to open a browser to a registration page with a CAPTCHA, or to require separate signup via web, because API signup was seen as vulnerable.
Now most apps seem to offer registration via native form, though endpoints for this are usually not documented in their public API. I haven't seen many reports of this being abused to create spam accounts.
How is this done? Is there a standard crypto/handshake process to verify real signups, or does signup typically rely on undocumented endpoints and simple API key passing?
Embedding yields a better experience but has the issue you mention. Yes, the service owners on the other end are still worried about this and combating the problem. And undocumented APIs don't help and the service owners know this.
One of the tools in the toolbox these days is keys assigned to devices which can be used for throttling. This would essentially let you limit the amt of service that can be consumed on a per device basis and it would require you have a device (or can steal the key from one) in order to provide service. So long as the process to issue keys to new devices is strong (a solvable problem) then you can offer a CAPTCHA-free signup experience within the confines of what you are willing to give to a device.
I'd also note that there are other well known approaches you can use, like IP throttling and handshakes with other service providers (like a phone carrier). Depending upon the problem domain these are on the table too...