Agreed, though in this case, they are going for general-purpose OCR. That's fine in some cases, but purpose-built models trained on receipts, invoices, tax documents, etc., definitely perform better. We've got a similar API solution coming out soon (https://digital.abbyy.com/code-extract-automate-your-new-mus...) that should work better for businesses automating their docs at scale.
Congrats to the Mistral team for launching! A general-purpose OCR model is useful, of course. However, more purpose-built solutions are a must to convert business documents reliably. AI models pre-trained on specific document types perform better and are more accurate. Coming soon from the ABBYY team, we're shipping a new OCR API designed to be consistent, reliable, and hallucination-free. Check it out if you're looking for best-in-class DX: https://digital.abbyy.com/code-extract-automate-your-new-mus...
We get 1-5% response rates (which is normal; I've done this on a few sites now) but we have enough scale where we're getting enough feedback that I can use the data to identify the worst docs. The basic methodology is to prioritize the pages with the most pageviews + lowest helpfulness scores. Of course there's a risk that we're prioritizing our work based on data that isn't indicative of our overall audience and due to the general nature of the question ("was this page helpful?") we also don't know how exactly the doc is unhelpful but in practice it's usually easy to make an educated guess (e.g. one of the Lighthouse guides is very low rated, and when I checked on it recently I discovered it's just a stub with very little guidance; so the educated guess is to add more guidance to the page; and then a few months from now I can see if the ratings have improved). Another good pattern is to provide a freeform textbox for feedback. The only reason we don't have that is because Gooble considers it PII and I have to jump through hoops to store that data properly.
Just us out at [Ionic](https://ionicframework.com/) - a complete platform for doing just that. Write a web app using your framework of choice (or none at all!) then deploy as a PWA, iOS, Android, or Electron app.
Love love love Netlify! Moved my blog from Tumblr (lol - but it was free!) to Netlify with Hugo as the static site generator. A wonderful experience. With little effort, my blog now has SSL, auto-deploys after I git check-in, and is a million times faster. I wrote a tiny bit about the migration process: https://www.netkow.com/moving-from-tumblr-to-hugo-netlify/
Saw this on Reddit last night, poked around on a few pages. It's great! Love the movie list example on this page: https://github.com/bpesquet/thejsway/blob/master/manuscript/.... Going from "for" loops into map/filter/reduce concepts is an excellent way to teach!
Based on your main point, no experience, I have two suggestions: React/React Native for the framework approach, or something lighter: Simple HTML, CSS, and JavaScript. My background: .NET dev by day, Cordova dev by night.
React/RN and Ionic would be my top framework suggestions. With React, you have to learn their specific UI syntax/JSX, then React Native syntax. With Ionic, you need to learn Angular and TypeScript, as well as their specific UI syntax.
Another idea would be to start with simple HTML/CSS/JavaScript. These are the building blocks of the web and I've seen others struggle immensely when they don't take the time to learn them properly. This is what I did with my apps, currently using Knockout.js (two way binding is amazing), KendoUI Core (easy cross-platform UIs), and PhoneGap Build (cloud service to create native apps from web code). Incidentally, my Pluralsight course launches in a few minutes - http://www.pluralsight.com/courses/phonegap-build-fundamenta... - and is exactly meant for beginners to get their feet wet before diving into the more complex frameworks.
Ah sure, sorry about that! I meant to elaborate but got distracted haha. Up until now, I've used plain web tech... but will be switching to React Native or Ionic soon. They both offer so much: rich UIs, native plugins, and more. So what I meant by my comments is, unfortunately I can't give more feedback on RN, but given its rising popularity it would be a safe time investment. I do stand by my comment that you could begin with vanilla web, then move to a more complex framework when you grow to that point. Thanks for the kind comment about the course, too!
Absolutely! Despite critics, they can feel native due to increasingly better phone hardware and picking a good framework (KendoUI Mobile, Ionic, React Native, Xamarin). I use KendoUI Mobile and Knockout.js for mine currently, with plans to probably switch to Ionic someday. Users don't care what the tech is - it's about the experience. I've sold over $100k in apps over 3 years... just launched an Untappd beer app if you're curious - www.getBeerSwift.com.
Here here! I do the same for my line of fitness apps. $3.99 at the moment. The only way for consumers to begin to understand that the software they use everyday costs real money to build and maintain is for us to charge for it. I'll be experimenting with higher prices later this year. Cheers!
