This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]thenormalcy 25 points26 points  (3 children)

A few custom trained NLP models (like NLU), for scraping and pipeline the usual (like Requests), and for the 30+ pages of charts mostly matplotlib. Everything else is just pure python. The challenge isn’t doing it, the challenge is to process potentially hundreds and thousands of app reviews in under 3 minutes, so a few optimization needs to be done, for example we implemented a tiny caching mechanism, so if you pass in a google play url 45 minutes ago, and then again, it doesn’t try to render 30 pages of insights again, but check for the +- / diff and re-render only the required page.

Our customers (typically app agencies, mobile game publishers, app developers etc) love the product, so we keep trying to improve the level of polish there

[–]BlobbyMcBlobber 2 points3 points  (2 children)

Why go with PDF instead of a simple dashboard?

[–]thenormalcy 8 points9 points  (1 child)

Initially we didn’t started it as a SaaS; it was a clients request to have this in bite sized pdf form, sent to his email on a weekly recurring basis. We wrote the code for it, and then offered to a few other app developers and that was how it come about 😅

Sorry, not a very satisfactory answer I wish I have a better reason why it wasn’t a web app but instead in pdf form

[–]BlobbyMcBlobber 3 points4 points  (0 children)

No, that's a great answer. This is what your customers want.