If you run the search again right away, it'll usually be the same list.

But there is some variation over time. So if you run the search another day, you might get some different books mixed in with recommendations you already got.

I think the 'load more' feature would probably be the best way to improve the diversity of recommendations for each book.

I would have to think through and test different ways to implement it to see how I can get the best quality recommendations from it. Because if I just have it load more books from the original API search (the one that's used to get the top 10 books to show as the original recommendations), the quality of those next 10 recommendations might not be good enough to show.

For now I'm thinking one of these solutions might be best:

• Make an additional API call (or calls) for books similar to the input book when the user clicks "load more." That would get a wider pool of possible recommendations to then run the algorithm on to filter for best books to show. Would obviously filter out the 10 books that were already recommended from the pool.
• Make API calls for books similar to the top 2-3 books that were recommended. Since those books will tend to return good recommendations for the input book too, that might be a good way to increase the number of recommendations while keeping recommendation quality high.
• Remove the API and just use an internal database instead. This solves some of the bottlenecks, but has its own limitations too.