I am working on an application that allows a user to scan through their facebook photos and then creates a slideshow, and ideally I would like to be able to have the option to publish as a book.
Im happy with the facebook part, and I assume the submission to your API is straightforward enough.
What I want to know is how then does a user purchase the book from you? I also want ONLY that user to be able to buy that book, so in essence a private purchase for them.
The pattern that most people follow with your use case is to publish all of the projects under a single account with an empty array for the distribution field:
This will ensure the product, while available for purchase via a direct link to the product page, will not be available through lulu.com's search and browse.
This is not strictly private, though. If your user decides to give that URL to someone, they will also be able to purchase it through their account, so you should be clear about that distinction. We are working to provide more powerful controls over who can purchase products, but for now this is probably your best solution.
I am working on an application that allows a user to scan through their facebook photos and then creates a slideshow, and ideally I would like to be able to have the option to publish as a book.
Im happy with the facebook part, and I assume the submission to your API is straightforward enough.
What I want to know is how then does a user purchase the book from you? I also want ONLY that user to be able to buy that book, so in essence a private purchase for them.
Message edited by soapcreative 2 years ago
Josiah Gore – 2 years ago
The pattern that most people follow with your use case is to publish all of the projects under a single account with an empty array for the distribution field:
"project": { ..., "access": "public", "distribution": [], ... }This will ensure the product, while available for purchase via a direct link to the product page, will not be available through lulu.com's search and browse.
This is not strictly private, though. If your user decides to give that URL to someone, they will also be able to purchase it through their account, so you should be clear about that distinction. We are working to provide more powerful controls over who can purchase products, but for now this is probably your best solution.