4 ms·

Thanks for taking the initiative. I would love to see more developers follow this approach.

ncr100 7y ago
Agreed: Cool app and certainly heroic and worth implementing. As an alternative, Google Photos from the App Store also support OCR for still-images on its web version. I don't have an idevice on me to know if it's also OCR in-app. Give GP a run for its money, Screenshot Hero!
- asadlionpk 7y ago
  Thanks! Yes Google Photos is awesome and does way much more (like searching by things in photo). I just wanted an on-device solution without having to upload anything to Google servers.
briandear 7y ago
I wouldn’t. Swift is far more performant than using these React-type pseudo-native systems and the developer mentioned that he “fell back” to React because of an apparent lack of SwiftUI documentation — so why not use this project as a chance to actually learn it and create some documentation? He wrote up about how he built the app, adding yet another article to the boring canon of “I just want to use JavaScript and React and call myself an iOS developer.” And he said that he used React just for the views — SwiftUI isn’t that hard at all and there are exact tutorials about listing things. Ray Wenderlich for example, the WWDC videos — there is high quality information out there but it seems like Swift and SwiftUI wasn’t actually a real consideration. To be clear, I am not criticizing the app, what I am criticizing is the parent comment hoping more developers follow that approach. I happen to think that approach is lazy and aspires to the lowest common device denominator rather than building apps that are platform specific and optimized for each.
- hombre_fatal 7y ago
  > so why not use this project as a chance to actually learn it and create some documentation Sometimes you just want to get something done rather than do free work for one of the richest corporations in the world. The latter should be enough fulfillment for anyone, but sometimes you're just too greedy!
- rhodysurf 7y ago
  I think that's unnecessarily harsh. RN is powerful and the dev still uses Native modules and views. The performance was probably good enough for this concept and he made a cool app with it.
- asadlionpk 7y ago
  This project was supposed to be that, a chance to learn SwiftUI. I didn't want to reverse engineer their API + document it. Frankly, I didn't have that kind of free time :) It helped that React Native performed great for this use case.

Agreed: Cool app and certainly heroic and worth implementing. As an alternative, Google Photos from the App Store also support OCR for still-images on its web version. I don't have an idevice on me to know if it's also OCR in-app. Give GP a run for its money, Screenshot Hero!

asadlionpk 7y ago
Thanks! Yes Google Photos is awesome and does way much more (like searching by things in photo). I just wanted an on-device solution without having to upload anything to Google servers.

briandear 7y ago

I wouldn’t. Swift is far more performant than using these React-type pseudo-native systems and the developer mentioned that he “fell back” to React because of an apparent lack of SwiftUI documentation — so why not use this project as a chance to actually learn it and create some documentation? He wrote up about how he built the app, adding yet another article to the boring canon of “I just want to use JavaScript and React and call myself an iOS developer.” And he said that he used React just for the views — SwiftUI isn’t that hard at all and there are exact tutorials about listing things. Ray Wenderlich for example, the WWDC videos — there is high quality information out there but it seems like Swift and SwiftUI wasn’t actually a real consideration. To be clear, I am not criticizing the app, what I am criticizing is the parent comment hoping more developers follow that approach. I happen to think that approach is lazy and aspires to the lowest common device denominator rather than building apps that are platform specific and optimized for each.

hombre_fatal 7y ago
> so why not use this project as a chance to actually learn it and create some documentation Sometimes you just want to get something done rather than do free work for one of the richest corporations in the world. The latter should be enough fulfillment for anyone, but sometimes you're just too greedy!
rhodysurf 7y ago
I think that's unnecessarily harsh. RN is powerful and the dev still uses Native modules and views. The performance was probably good enough for this concept and he made a cool app with it.
asadlionpk 7y ago
This project was supposed to be that, a chance to learn SwiftUI. I didn't want to reverse engineer their API + document it. Frankly, I didn't have that kind of free time :) It helped that React Native performed great for this use case.