This wrote a complete Laravel feature for me from start to finish almost perfectly, better than any other approach I have tried (e.g. TaskMaster). Amazing job.
I need to take the time to see what the Laravel side of this is so perhaps I can adapt for my RN app too.
From https://www.handwritingocr.com - seemed to be more accurate, mostly getting the New Mexican and possibly other parts:
---
and I don't know whether it can be reset for a date in December or not. Cornell seemed anxious that it should not come off too close to Christmas, and of course New Mexican practice would support him. I will take this up with the Judge and with Hanna the moment I can get rid of the brief. Meanwhile I would like to know whether there is anything else in which I can be useful to you, since it behooves me to be diligent in view of uncomfortable relations with the present management.
Are you going East in December?
Has any word come from Hagerman?
Were there any noteworthy developments at the hearings on the Tenorio tract?
I have no intimation yet whether I will be wanted in Washington, but the chances are that I will not.
I'm the founder of handwritingocr.com - have you checked out our free trial? We have loads of educators using our service for exactly this, and they seem quite happy with it.
I understand your concern, and it's a common one. However, we can only give assurances in our privacy policy that your data is used only to perform the OCR, and nothing else. You can delete all data from the server immediately after downloading your results and no trace will be left.
Of course a local solution like Ollama is preferable for privacy reasons but, for now, the OCR performance of available local models is just not very good, especially from handwritten documents. With a couple thousand pages of journal entries, that means a lot of post-processing and editing.
It's not free, but its accuracy for for handwritten documents is the best out there (I am the founder, so am biased, but I'm really excited about where the accuracy is now). It could save you time and for your 100 page project would cost only $12.
True, in cases like OP a one-off purchase will be better. But I also have business customers with regular and ongoing document processing needs for whom a subscription does work.
I expect the answer may be a combination of the two.
I’m still experimenting with pricing, and agree that per page pricing makes logical sense. Still, it’s harder for me to build a sustainable business on that model.
I will probably test a few per-page or single payment options soon, though.
It is designed to do exactly what you are looking for, and has been used very successfully by many others for that same purpose (I’m the founder).
It is not as cheap per page as Google Document AI, for example, but it does tend to be much more accurate for handwriting, so usually ends up cheaper when editing time is factored in.
If you find it does work well with your handwriting, please get in touch and I can try to fit the pricing to your use case.
I left my last job and a toxic boss a few months back and decided the only viable future is to start my own thing again. But this time I was going to do it properly - lean customer development, speak to users before writing a line of code, etc.
Instead, I became fascinated by the massive improvements in OCR and how they can be applied to digitising boring paper records. Decided to start out with the most boring problem of them all - credit card and bank statements.
I decided this would also be a great project to make the leap to Python and Django. So, without speaking to a single potential customer, I threw myself into coding. After a while, I realised Laravel is so much better and jumped back to that. Have learned loads as a result.
I've built a local prototype that works really well with impressive accuracy. However, I noticed the signs of fatigue and self-doubt that often mean a project is abandoned at 80% without seeing the light of day.
So I decided to find a domain name and put the totally half-baked and not-yet-functioning version online. A crappy, embarrassing, non-functional version. But at least I might get some feedback, which is more likely to inspire me to keep going and work out how I could market this.
I'm giving myself a week or two to refresh, then will press ahead some more and put the minimal functionality online while thinking about how to find users.
Everything is done with real time calls to the eBay API. eBay's catalogue is too large to make it realistic to fetch it as a whole and, anyway, as far as I remember they don't offer a data dump (it's been a long time since I checked).
Luckily, eBay's API is very fast, but I also worked hard to keep the total response time of my code within a reasonable range.
I need to take the time to see what the Laravel side of this is so perhaps I can adapt for my RN app too.