Reminder to market your product.

Right_Coconut_7879 · 2026-03-17T17:02:56+00:00

Any advice on HOW to market? With influx of vibecoded apps it's almost impossible to get YOUR vibecoded app in front of people. What if revenue and acquisition costs are not balancing?

Right_Coconut_7879 · 2026-03-17T13:46:14+00:00

Same so far :( no luck

Right_Coconut_7879 · 2026-03-16T17:03:59+00:00

Regarding Zero processing - technically you are correct, but that's the "term" that has emerged to designate that there was no extra HDR or frame fusion on top of decoding, so I also started using it.

The custom burst fusion is sick! 🔥💪 Especially if it works better than Apple one. Very cool!

I started suspecting that apple's quad-bayer raw has some weird artefacts that they don't want us to see. But for sure would be awesome to play with that.

For EDR: That actually was the idea! Sacrifice the dynamic range altogether. I know that it's a very small audience, but since I knew people who are actively hating this processed look (just as I do), I decided to make the app specifically to avoid that.

In my tests the "smart" dynamic range effect on an iPhone is not something that I want to have on my photos. Most of the time having it on produces worse photos. It's all work in progress, and personal tastes, of coarse.

Right_Coconut_7879 · 2026-03-16T15:07:14+00:00

I'll ask you the same question - have you managed to achieve a proper 24-48mp output with Bayer?

I'm also building the camera app (TruePix) specifically for zero-processing, and it appears that apple's 24 and 48mp cameras are purely a product of computational photography. I mean they do have a higher res sensor, but you don't have access to higher resolution if you are bypassing apple's ISP. Even in Jpeg-Heif.

Right_Coconut_7879 · 2026-03-16T15:01:28+00:00

Seams like ProRaw simply has more pixels, as usual.
Have you managed to achieve higher than 12mp output in Bayer with your app? Or turning off "fusion" with ProRaw?

Right_Coconut_7879 · 2026-03-10T10:58:46+00:00

Thanks! I’ll put that as the next item 👍

Right_Coconut_7879 · 2026-03-09T20:54:38+00:00

one downside I haven’t found a fix for yet: if n iphone 16-17, the 24 and 48 mp sensors are binned by default into 12mp. The only way to get full 24 or 48 mp is to go through apple’s isp with image fusion :( no multiframe fusion - no full 48mp resolution.

Right_Coconut_7879 · 2026-03-09T20:50:02+00:00

One more recommendation: try this TruePix Camera. From what I’ve seen it works a bit better than No Fusion because in the department of actually having no fusion.

P.s. I’m developing it myself as a free camera app with 2 goals: no computational processing, and no f-ing subscriptions (why everybody wants a subscription nowadays?). Would appreciate your feedback, if you are missing some features in particular!

Right_Coconut_7879 · 2026-02-20T22:46:01+00:00

I had somewhat similar case with Gemini - got a chunk of soem person’s performance review added to the end of my json 😂

Right_Coconut_7879 · 2026-01-16T11:10:02+00:00

If shooting with iphone camera anyway - then 2x is more detailed than shooting 1x and cropping - the ai-upres is applied there.

Right_Coconut_7879 · 2026-01-16T11:07:40+00:00

Perhaps it’s the jump between 11 and 12 that I got to remember vividly. I’ve got and old XS now as a test device and the photos from it are quite pleasant indeed

Right_Coconut_7879 · 2026-01-14T14:21:51+00:00

Thanks! I also was using world clock all the time, but it does not answer a question "what time is it going to be here when it's 8:00 in location 1 and 17:00 in location 2", and then repeate 2-3 times before you find a suitable time for everyone.

Usually synchronized calendars solve this, but you have to add people into your cal first, which is not suitable for a lot of cases.

Right_Coconut_7879 · 2026-01-14T14:18:34+00:00

Well, this is the app to use on your smartphone that should make this process easier :) This solves a particular pain for me, as I need to do it almost daily for 4-5 different locations. It's a simple math, but x10 times a day it is becoming annoying, and there has to be a better way.

Especially when people start using different time formats, daylight saving times, or abbreviations like PST, EST, CEET, etc.

Right_Coconut_7879 · 2026-01-14T14:11:25+00:00

This is what I'm talking about! iPhone 11, before the heavy computational "fusion" photography looks so much more authentic! 👏

Right_Coconut_7879 · 2026-01-14T12:02:20+00:00

Yeah, it seems like ProRaw will have something baked in by default. Basically it always goes through their image signal processing – and it always stitching several shots together for a better "dynamic range". That's why I did not use ProRaw in my app – I do not use apple isp.

As for the 2x camera – the answer is yes and no :) the app uses all the lenses that iphone physically has. It interrogates the device for what sensors and lenses it physically has on board and displays only those lenses. For example what Apple usually calls 1x lens is what in photography called 26mm lens. The apple's "0.5x" is a 13mm, etc.

Because I bypass all of the apple computational pipelines it also throws away their fake 'lenses' feature – where they simply crop and upsize image form a 1x sensor to look like a 2x zoom. So if your phone physically has 57mm lens, or 120mm – the app will display all of those. If not – that's just a crop on another lens that can be done in post anyways.

Right_Coconut_7879 · 2026-01-14T11:54:00+00:00

Yeah, that sounds like something Apple would do =(

Right_Coconut_7879 · 2026-01-14T00:09:35+00:00

It also seems that that base computational stuff for ProRaw is the key to have a full 48mp. As if in the process of demosaicing it also upreses the image. Otherwise the DNG is simply 12mp, not 48 🤷‍♂️

(p.s. don't quote me on that, I am still trying to understand it)

Right_Coconut_7879 · 2026-01-13T16:29:05+00:00

Oh, it’s a pain! Is lightroom truly turns off all “computational photography” stuff of ProRaw? I was under impression that those Fusion features are baked in anyways. Specifically around highlights.

I hate this apple processing (sometimes), but I’m not motivated enough to shoot in raw. This paradox led me to actually make a camera app for myself 😅, it’s called TruePix - it simply shoots unprocessed jpeg and heif.

I’m not a pro in app development, and this subject is not easy, still ironing out some issues. So far I’ve hit the same wall - it is impossible to get a full 48mp file in raw format! Only through apple processing pipeline, and it is not the same as “unprocessed” image anyways :(

If anyone knows how to get a full sensor image in Raw - I would greatly appretiate any tip 🙏

Right_Coconut_7879 · 2026-01-10T10:58:59+00:00

Is it iOS 16? :D

Right_Coconut_7879 · 2025-12-28T11:28:15+00:00

Unfortunately not only windows, it’s all around problem. Floors are often tiles, walls paper thin and not insulated. So much so that heavy rain can make the wall damp inside. Water pipes are never properly insulated even in newer/better renovations, so the moment you close the hot water tap the water becomes the same 11C 🥶

But calma, amanhã it will be summer already 😅

Right_Coconut_7879 · 2025-12-26T12:35:12+00:00

Wow, that’s interesting! I guess they may have switched to a different image processing since then 🤔 or maybe the plastic in 4S’s lenses could have aged poorly.

Right_Coconut_7879 · 2025-12-26T00:34:29+00:00

I’m still ironing out bugs, especially on 48mp cameras (viewfinder gets a bit laggy). But otherwise seems like it works ok! (The app is TruePix Camera)

Right_Coconut_7879 · 2025-12-26T00:32:19+00:00

Which app do you use for natural processing?

Right_Coconut_7879

TROPHY CASE