|
To onboard or not to onboard
As many of you know, I've been having a lot of 'fun' onboarding people to The StoryGraph.
Being able to click a button and magically have all of your Goodreads books loaded into your account is something that I'll have to get to eventually...
...but, is it? 🤔
Right now, it seems a bunch of people are fine using the app without their whole library being loaded in, but are they being patient because they know we're in beta?
Some questions that y'all can help me mull over (feel free to reply to one, many, or none):
- Should I worry about the onboarding problem now or focus on other core features instead?
- Maybe it's worth changing people's perception that they need all of their Goodreads history in this new app?
In the words of one beta tester:
My "to read” list needs a good clean out. There's loads of old things I added that I will likely never get round to reading, so a clean slate there might be a nice fresh start...StoryGraph is interesting because it lets me search for books in a way that I’ve not been able to do before, so previous read/to-read data isn’t that helpful/accurate for this new system.
A "Start 2020 with The StoryGraph" campaign, anyone?
- What if I offer full onboarding to people who really care about it right now but charge a one-off fee, since it involves manual work? 😬
A snapshot of my Goodreads library export
In the meantime, I have a script that acts as a compromise: it can take anyone's Goodreads library and sync the user's account with any books that already exist on The StoryGraph.
If you'd like me to run this script for you, let me know. 😊
|
