In our company, we have a competition called BookQuest. Every week we read professional books, and after every read page, individuals receive points - we compete to win the event by reading, learning, and improving. It is a friendly competition, but it motivates us - and every Monday the winner is celebrated. This was our inspiration, and we created Booxly exclusively for this hackathon. ⭐

What it does

Booxly is an automated bookmark system. It summarizes the read pages, monitor reading habits, and could help the users to reach their reading goals! After every completed book, Booxly generates a shareable image - so we can share it on Facebook.

We aimed to create the most significant impact on our user's life with the least energy investment on their end. So the app is extremely user friendly and easy to understand, while by its functions the users can improve themself every day.

How we built it

• We used our own Node JS chatbot framework for the chatbot intelligent

• We used our custom #C image generator system for the generic template

• We have done a lot of UX testing and pretotyping

Challenges we ran into

• We wanted to use a book database because of the covers, but we couldn't find any online that contained vintage and local books as well. So we allow the users to take a photo of the covers of their books, and upload it.

• After that, we wanted to receive the cover photo inside the conversation - we planned to automatically identify the book cover on the picture, cut it out, and distort to remove the perspective. We didn't have the result we hoped for, so we moved forward with a manual cover cropper, that could be used inside the webview.

• We had to generate default covers for the book - because we need a cover image to we can use for the generic templates

• We had to prepare different user flows for Bookmark saving, based on the bookmark page number and the number of active books - it needed a lot of UX testing. We created a smooth experience for the users.

Accomplishments that we're proud of

• The user flow is smooth and so easy to understand to use! We spiced things up with the server-side generated generic template images.

• The conversation looks astonishing with the rich graphical communication (in our opinion).

• The book cover cropper was a great idea; it is much easier to use and increase the UX.

• We created an app that we will use every day in our company - we are proud of our team's effort.

What we learned

• We researched the essential user needs we need to fulfill - luckily, we already had experience based on our BookQuest, but things are a little bit different in a chatbot.

• To see the book's cover is essential; this way, users can connect the digital books with the physical one. We use the conversation interface as a controller and logger; users can review their behaviors.

• After we finished the development of the conversation design, we identified a new need. Sometimes, it is easier to handle and oversee our statistics in a GUI, so we created UI for webviews, where users can use every function.

What's next for Booxly

  1. We will make Booxly multilanguage so that it will become an international application; we will start with 🇭🇺 Hungarian.

  2. We will include a notification system - users can set up notifications to reach X pages every week. (we planned to do it in this Hackathon, but we run out of time 🕒)

  3. We will include a gamification system - we will reward users with points and badges, and they receive quests every two weeks:

Badge examples

• Book worm - Read 300 pages a day

• Read Sprint - Finish a book in 3 days

• Page Chain - Read five days in a row ...

Quest examples

• Read %500% page in 2 weeks

• Finish a %Fantasy% book in 2 weeks

• ...

  1. We want to recommend books after a user finished one book - based on the category, writer and title

Our team

• Csézi • KZ • Tom • Yusuf

Share this project: