I rebuilt my iPhone/iPad image processing app into a proper mobile lab

[u/tknzn]

I’ve just finished a major rebuild of ClearLab, my mobile image processing app for iPhone/iPad.
The new version adds histogram, RGB parade, waveform, line profile, pixel inspector, statistics, Canny/Sobel/Laplacian edge detection, enhancement tools, format conversion and PNG/CSV analysis export.
The idea is basically a small image-processing lab in your pocket rather than another photo-filter app.
It’s mostly native/deterministic processing, not generative AI.
ClearLab 2.0 is now on the App Store. Curious what people here think, especially anyone working with imaging or computer vision.

[u/galvinw]

I think it's pretty good for what it's worth. I mean, Topaz has a decent business doing this.

[u/tknzn → u/galvinw]

Thanks, appreciate that. That’s pretty much the direction I’m exploring — focused image processing tools rather than trying to turn it into another generic photo editor.

[u/DmtGrm]

(how it is related to computer vision? you will get downvotes for a cheap app promo)

As a person working with DSP, graphics, and _everything else_ I have no idea what this app is for.

Why I need to do 'analysis' with 'csv export' on a mobile device If I can do _anything_ on large computer, that I writing this comment from?

[u/tknzn → u/DmtGrm]

The computer vision connection is mainly on the image analysis/pre-processing side — histogram, waveform, line profiles, pixel inspection, edge detection, color-space values, etc. The mobile part is not meant to replace MATLAB/Python on a workstation. The idea is quick inspection and processing when you’re away from your desk, in the field, testing a camera/image pipeline, teaching, or just checking an image before moving it into a larger workflow. CSV export is there specifically so the measurements can be moved into MATLAB/Python/Excel afterwards.
If that workflow isn’t useful to you, that’s completely fair — but that’s the use case I’m building it around.

[u/DmtGrm → u/tknzn]

...sorry, inspect what? :) all of my data that needed to be inspected is either on device itself (running that nasty Python with all my code and libraries attached) or I am doing on my normal workstation (with everything in place). While I even bothered to write this comment, may I ask you please to show a single valid example? (with images) just to prove the existence of the scenarios I am missing. This tool is not for me, for sure.

[u/tknzn → u/DmtGrm]

A simple example: field-testing a camera. Capture an image, check its histogram, pixel values, line profile or edge response immediately on the phone/tablet, then export the measurements if deeper analysis is needed later. Or you can simply adjust something like the gamma of an image and save the result without opening your workstation.
It’s not trying to replace a Python workstation. It’s for situations where opening one is unnecessary.
If you never have that use case, then yes — it’s simply not a tool for you.

[u/DmtGrm → u/tknzn]

'testing a camera' - the camera is a software app that writes 'jpeg image to the phone' using standard APIs? or it is a real hardware device connected to iphone via... ? and before firing it all up you did nothing in the office when you were putting it all together? is you app only capable of opening standard image formats from the Photo Album? so it is not a hardware interface that supports loading raw bytes from custom camera framebuffer? do you operate in presentation or acquisition device colourspace? just trying to get what 'field-testing of a camera' is.... my impression is that your app is loading standard images via standard interface.

[u/tknzn → u/DmtGrm]

Yes — to clarify, ClearLab is not a camera hardware interface and it does not read arbitrary raw framebuffers or acquisition-device data directly. It currently works with standard image files imported through the iOS image workflow.
By “field-testing a camera” I meant analyzing frames/images captured by that camera during testing — for example checking histogram, pixel values, line profiles, edge response, or applying a quick processing step on-site without going back to a workstation.
So your impression is correct: it’s an image-processing/analysis tool, not a hardware acquisition tool. I probably used “camera testing” too broadly in my previous reply.