To be honest, I wouldn't be surprised if Apple isn't already doing this and just doesn't say so explicitly. There is a crazy amount of image processing going on behind the scenes in each smartphone photo. Would be interesting to compare a photo taken with the native camera app and photosynthesis to compare. I'm assuming your demo images on your site are the raw and processed images from your app that don't go through Apple's "secret sauce" processing pipeline.
Hijacking this comment because of this line that reminded me of something:
"There is a crazy amount of image processing going on behind the scenes in each smartphone"
I bought the Pixel 10 because it said it had great zooming capabilities. After 5X (that means 10X), it's completely stupid. Basically it takes a very blurred photo and then tries to reconstruct it with AI. The final results are completely awful and really distant from reality.
In photos after you can toggle between the AI modified and original. The original isn't as blurry as the preview shown - there's still a lot of image stacking happening and it's often very decent in my experience.
Edited to add: I have a pixel 10 pro which has a better zoom lens, so I could be having a different experience than you...
Also have a 10 pro .. but the AI-enhanced zoom goes up to 100x and is actually pretty handy for working out what tiny things in the distance actually are ... even if it's only a representation of that thing. Often use it for identifying birds, boats, etc.
I think my p10p's 100x zoom is neat, but I'd strongly caution against using it for ID in any sense, or necessarily even treating it as a photograph. It will "straight up hallucinate" objects into existence, more of a creative interpretation of 100x digital zoom than an oracle into the identity of something far off.
Makes for a fine image if "looking good" is the objective (which it often is), but I wouldn't trust it to disambiguate anything uncertain.
The biggest of the "sharpening with AI" models, if you let 'em go, they'll turn you into a celebrity on accident.
If you go to the Topaz AI forums on Facebook, you'll see examples of where the AI sharpening tool went off the rails and turned a blurry photo of someone (typically the user who bought the software, who is trying to clean up their own photos) into whichever celebrity that is in the AI model who resembles them.
IE, it might turn a photo of YOU into a photo of Robert Downey Jr.
A couple years ago, we needed a good photo of my grandfather for a photo collage. The best photo I had of him was where he's sitting next to a very decrepit looking old woman (some family friend?). It really was a great composition, great lighting, background and pose but the old lady was killing the vibe. My wife is really skilled at Photoshop but removing this old lady would have been really difficult so we decided to try the generative fill, something she had never used before. She selected the lady and typed in "delete this person". Instead of deleting her, it creates this strange, human like being. We try again and again with different permutations of the same command. Most of the attempts just replace the old lady with a small asian child. Eventually we just try with a blank prompt and it gets it in the first go. The Asian child thing was really strange, it truly looked like the same kid but just slightly different appearance each time.
Also wonder how how long until photos are no longer court-admissible evidence because they get overwhelmed with the burden of the amount (and the cost) of the "non-AI" certification?
We've been living in the age of photoshopped photos for decades now. You can't just present a random photo as evidence without being able to back up its provenance.
As long as you know how to edit metadata, you can definitely fool minor “trust systems” like adjusters, police, etc. It’s a big gap. (For any future readers, no I have not done this and would never do it, really.)
The only solution I see is some kind of hardware-linked signature showing that the image was produced at a certain time, by a certain device. In theory, you could make this signature somewhat “provable” and anchored to a specific time by combining something like 1) the latest Bitcoin block hash, and 2) a blockchain anchor, thereby proving that the photo was taken within a certain time widow after the hash was known and before the anchor was published. But even that arrangement is highly susceptible to hardware attacks.
The ENHANCE meme used to drive me nuts because it is clearly impossible. My brother and I even briefly competed to find the earliest ENHANCE reference (I no longer remember what we concluded, but it goes surprisingly far back). The fact that it actually exists now is mind-boggling (even though it is, by necessity, still a fiction).
Yes exactly, the site shows photos all taken from within the app. I have done A/B tests against photos taken in Camera.app and the Photosynthesis composite does significantly beat the detail central area covered by the second lens in Photosynthesis.
Because of the limitations of capturing multiple lenses at once through isVirtualDeviceConstituentPhotoDeliveryEnabled, there is a second capture mode in the app for 'Quality' which takes a simultaneous capture then takes sequential shots from each lens which do benefit from Deep Fusion, then uses those for the stitch (as long as the Deep Fusion images outperform the simultaneous capture results). That's also what I do for our Night mode.
Phones have been doing this for a LONG time, if you had a oneplus 7 pro (released may 2019) and took it into an extremely dark area, like where your eyes can't see anything at all, and take a 'night mode' photo, it asks you to hold it steady for about 4-5 seconds and is clearly taking a series of photos with long exposure time. Then it stacks them and uses data from the sensor of hand movement jitter to deblur.
The result when done outdoors (like, standing in a dark forest at midnight) will be a photo where you can actually see what's around you, and details show up as if it was a brightly full moon lit night.
I know, I just don't think it's a huge jump from "take multiple photos over a 2s period from one camera and stack them" to "take several photos from discrete physical cameras and stack them". As a subscription of paid app I am not the target market for the person who made this, I agree with another person commenting in here that said they should be working for a phone manufacturer.
I’d argue the opposite. The geometry involved in reconciling photos from two separate lenses with different focal lengths is quite challenging. If you pay close attention you will see some differences in the before/after samples in the site (for example the ear in that kitchen selfie).
The math is surely more complex than aligning same-lens photography even when you consider the change in angle and perspective between two shots from the same lens.
The Amazon Fire Phone did this in 2014. I'm not aware of any prior art in mainstream devices aside from gimmicks like 3D (stereoscopic) photos. I can't remember if the Fire Phone had any relevant gimmicks but it certainly used multiple lenses to produce a single image.
UAV sensor people made a thing that uses 300+ phone size sensors in a single pod, and software workflow to fuse the output together. It's been around quite a few years now.
Night Sight appeared on the Google Pixel camera app in 2018. I think Nokia was doing it first on phones before Microsoft destroyed the remains of their phone business.
The reborn Nokia/HMD was also doing multi-sensor image stacking back in 2019 on the Nokia 9 Pureview.
It's different from just stacking exposures, it's a paid app that does progressive animation of exposures for creative effect and says it's "AI-powered" whatever that means.
It's a paid app that I literally have, and all it does is take multiple photos and composite them together. It can either naïvely average them together in-place like a traditional long exposure, or align them using machine learning. I'm actually appalled they use the term "AI" considering who they are but that doesn't matter, it's ML. I don't use any of the animation crap, but the aligned long exposures can be useful for ultrawide takes since that camera is so noisy.
Edit: actually I can't seem to find the setting that aligns them. I seem to remember it being able to do that but maybe it doesn't... which would be disappointing...
> I'm actually appalled they use the term "AI" considering who they are but that doesn't matter, it's ML.
I agree, and I built it!
The app launched in 2019. Ideally I would have said ML, but it felt like AI had more recognition among non-technical users.
If I launched it in 2026, it would 100% say "ML" not only because it's more technically accurate, but to make it abundantly clear it doesn't generate slop.
I use iPhones (paid for by work) as a tool for my agronomy job. I take a large amount of photos throughout the day to help document what I find in the field.
Since at least the iPhone 12, holding the phone still and letting scene sit for a few seconds will result in a sharper photo. I’m not sure if it’s a subtle version focus stacking or a sharpening algorithm, but it’s definitely there.
On my 16e, immediately looking at a photo just taken can result in the image noticeably sharpening after a second or 2, so this may be a post processing step as well.
From what I can tell, it's taking multiple photos and stacking them in post. So giving the phone more time to capture sharp exposures to stack would do a lot to help.
One time I took a photo of a snake in the road with my iphone in low light. When I looked at the photo afterwards the snake was removed by the AI enhancement
Somewhat related... I made an indie app called TwinCam which combines front-and-back camera images to create a combined selfie. Free. No strings attached. Cheers!
I have a Motorola moto g stylus 2025. I have not altered the OS or installed a custom rom. I simply have not signed into Google yet. I use aurora store to download and install app updates from the play store. What I'm curious about is why some apps won't even open at all without a Google log in? Is there something in your app that requires a Google account?
It would have been nicer if the examples wouldn't have been digitally altered to exaggerate the results. For instance, the center of the third photo has been intentionally blurred in the "standard photo" version.
The fact that they have to resort to manipulation to sell their product tells me that they are not trustworthy and that their product is probably underwhelming.
Thank you! I'm quite a new dev so honestly I don't know where to pitch the free tier, and I'm not above changing it. Do you have any suggestions for the free tier?
This is hardly convincing. A $99/yr fee and a once every 2 years update doesn't warrant a monthly subscription fee from every user. Eg a $9.99 app could cover those costs with a few dozen downloads
Why can't we be just... done? Why is software development a never ending treadmill? App does what it's supposed to, the developer earns something (or doesn't), and they can I dunno, abandon it if it wasn't successful enough and the API breaks, without any guilt? Do something else with their life?
OK? That's just the reality of business. You launch something and then need to do marketing to keep getting it in front of people until word spreads around that your app is a must-have thing for whatever it does and you get a decent number of sales every month.
In general, when I buy something I want to pay for it once and then have it. I don't want to rent or lease it, even if it's consumable. When I eat a restaurant I I pay for the meal when it's over; if it was delicious I might come back again. Even if I like it so much that I eat there every week, that doesn't mean I want a weekly subscription.
A restaurant can do just fine by making you a good meal every week, knowing you'll come back and pay them for each meal.
An engineer with an app can come to work 365 days a year, fix bugs, add nice new features, unbreak the app every time iOS updates, and, though you use the app every day, they can't count on you to give them another $5 every year - or ever again - unless you enter into a subscription.
This isn't to say you have some obligation to do a subscription to any app you don't think is worth it, but for apps from non-scam developers, they're usually like $20 or less a year - about a nickel a day. A nickel is 3¢ in year-2000 dollars btw.
It's on the developer to prove to you that the app is worth paying a nickel a day to have! But ruling it out just because we wish it didn't have to be, well, that just rewards the developers who monetize exclusively with ads or sell their 'free' apps to sketchy operators.
I'd like it if Uber was free or just cost a buck a ride flat rate, but I know that anyone willing to give me a ride on terms like that is probably looking to rob me.
Who expects 'nice new features' from an app they already decided to buy? Keeping the app compatible with new OS releases is necessary to keep sales going.
After a year, I don't think anyone is bothered if an app becomes unsupported for whatever reason. Usually what happens is the opposite - developer unnecessarily cripples an existing, perfectly working app, to try to milk some more revenue out of it.
This is an especially moot point now that most platform API upgrades are $1 of LLM work away.
> Who expects 'nice new features' from an app they already decided to buy?
I was just listing one more thing a developer who wasn't slacking might spend his time doing, that's all.
> Keeping the app compatible with new OS releases is necessary to keep sales going.
Relying on constant sales to new users sounds like a pyramid scheme. Software licenses don't wear out like shoes or become consumed like butter, with happy customers returning to buy more. Eventually, most of the people that need most apps have bought it and sales don't "keep going" more than a trickle, except for apps that are such mainstream hits that your new users are just "everyone who became old enough this month to get their first phone." And because the App Store has ruined organic discovery, paid apps rely almost exclusively on paying for installs either via Apple's ads or elsewhere. So, that eats a good part of each new sale's revenue right away.
Check the iOS top charts right now. For paid apps, the top-selling app is Shadowrocket, a rule-based proxy utility. How long until all developers who want a rule-based proxy utility have already paid the $3? If 100,000 developers buy that app, then that developer nets $210,000 pre-income-tax. About on par with a good corporate SWE job outside of FAANG. But that will slow down. There just aren't that many people who are looking for that. #2 is just a client of a subscription service for businesses. #3 is AnkiMobile Flashcards at $25. See, at that price I agree it can afford to never charge again. #4 is an ephemeral app for some art event in Portland so it doesn't need to be sustained. #5 is Procreate Pocket. I guess there are enough new aspiring artists appearing every day who can afford these apps (I think it's $13 for iPad).
> After a year, I don't think anyone is bothered if an app becomes unsupported for whatever reason.
Okay, so subscribe to the apps you use, and then immediately go in and turn off renewal in Settings -> (your Apple ID) -> Subscriptions. There. You now have a one-time purchase of an app which will stop working in a year - just like apps that have no recurring revenue stream do.
> This is an especially moot point now that most platform API upgrades are $1 of LLM work away.
I don't think you are a developer of serious iOS apps. Just the visual changes, that users expect apps to go along with, require major redesigns. People don't buy apps that look like they were designed in 2019.
We seem to be arguing at cross purposes. I am not saying that software is not worth paying for. $20 seems a very reasonable price for an application if it meets a customer's needs, and the only expectation I have beyond that is that it continues to work across OS updates. I'm OK with big version upgrades being a separate sale.
It's not the amount of the payment. It's the subscription model I can't stand. You're correct that I might use an app I like every day. But the marginal cost to the developer of me using it every day is $0. Rather than belabor the restaurant example , consider a book or a music CD. Writing books or recording music is generally a slow and difficult process, it takes months to produce one that might be read in a weekend. But if you buy a book, you can read or refer to it every day without paying again, or you cna listen to your favorite songs as often as you like by playing the CD. Nowadays many people prefer to stream music, but I think when people buy a book (even an e-book), they consider that it's their copy to read as often as they want...
...or not. If I buy a book and I don't like it, or later I find another book that I turn out to prefer to the first one, I can just not read it again. I don't have to cancel a subscription for the book.
This is where I get to with a lot of non-crazy people (the crazy ones just won't pay for software). Since you are fine paying $20 for a useful app, a $7 a year subscription can be better than a $20 one-time purchase in meaningful ways.
It aligns your incentives with the developer very well. They really want you to not cancel your subscription after only paying the first year's payment (when you may not have even paid back the customer acquisition cost!), and you want the app to be high quality and well-maintained. If the developer doesn't meet your bar for that, you cancel the subscription with 4 taps and they lose future income. That incentive to please customers after the sale just doesn't exist in a pay-once app world (except in tiny niches of old-school developers, like the Panics of the world, whom I do greatly respect).
Besides the incentives, it also gives you a chance to, after that one-year $7 spend, re-evaluate "do I even use this anymore?" If you paid for a guitar tuning app and you stopped playing guitar, you can just cancel the subscription, even before you've paid the amount that they'd have priced it for one-time-purchase. There is upside for the consumer in the apps that either let you down, or that you simply realized you no longer need, and it lowers the risk bar to try an app that you aren't sure about.
I get that if you do end up using such an app for the next 15 years, yes you'll probably pay somewhat more than any price you'd have considered paying one-off, but it also probably means that app (an app you use often for decades) couldn't have been sustained for all that time with only new customer installs paying the bills.
> if you buy a book, you can read or refer to it every day without paying again, or you cna listen to your favorite songs as often as you like by playing the CD.
We agree that this is all very great. And since the music or book you buy carries zero support burden of any kind from the artist it's a pretty great model - after their album launches the artist can devote 100% of their bandwidth to producing new music, or they can tour to get recurring income out of the same music, or a mix of the two.
You're using a device with an ever-evolving OS that constantly breaks compatibility.
If you paid for it once and only got to keep the version of it as of when you paid for it, in a couple years the platform would remove your ability to use it.
Even when you paid for software in the Good Old Days it was guaranteed to be compatible with ONE version of your OS, e.g. Windows 95. When you upgraded Windows, you'd often need to buy a new edition.
Even that's not really true. Most software that ran on Windows 95 could be run without modification or even a single update on both Windows 98 and Windows ME. Even XP preserved compatibility for most programs, adding explicit compatibility modes you could enable for an application that wouldn't work out of the box.
So, in the old days, you paid often $50-500 for a piece of software and the developer would usually have zero burden to update the software for you. By the time the OS completely broke it, it would have been 5+ years later. All that time, the developer was freed up to build and sell whole other applications, or, to innovate new and compelling features to get you to pay the upgrade price to get a new version.
Today that developer would have to do 5 major updates with breaking API changes, and probably at least 1 full visual refresh just to keep up with Apple's changing design whims, just for that one app to not be bricked. They have less bandwidth then to build more apps, since each app carries its own annual burden of churn.
I’ve been at it over a decade now and still found the only reliable way to make money from offline App Store apps is good old fashioned paid apps, $2.99 being a nice sweet-spot.
If you had customers buying last year, it’s likely you’ll have even more customers buying next year. If you stop maintaining your app, that stream of new sales almost immediately dries up.
Offline mobile apps which charge a subscription are a very silly fad to me. The few that get away with it are being steadily edged out by someone else who wants to eat their lunch.
I love the OP’s idea and absolutely see the use case. I also think it’s very promptable. My unsolicited advice is to strike while the iron’s hot at $0.99, because I’d be very skeptical if they’ll attract enough subscribers before getting starved out by copycats.
Yes they do need it to be maintained because they update their phone and any apps that don't keep up can no longer be used unless the dev does more work.
In 1995 or even 2001, this was a completely reasonable line. Most software was written for Windows, and Microsoft clearly considered it taboo to break old software, whether their own or third-party. You could install Office 95 on Windows XP if you really wanted to, which didn't seem unreasonable, as you spent $300+ on the suite.
Giving this advice to developers today is frankly absurd career advice.
1. Few apps can achieve the scale needed for a one-time fee to be sustaining for the app - most apps appeal to a finite set of people, and eventually most who are in your target market (and who are willing to spend actual upfront money), have bought the app.
2. An entire generation has grown up that has never paid more than maybe 99 cents for software, and most refuse to even pay that - they're used to adware. You can't price an "app" at $75 and expect it to be bought by essentially anyone. While adware can actually be a very financially viable route, many developers hate ads and want nothing to do with this model.
3. Unlike the multiple years of stability of old desktop operating systems, platform owners today think nothing of breaking even a plurality of apps with any major OS version - and for some insane reason they also think a new "major version" ought to come out annually.
If you want apps that cease getting updates after a few months and age very poorly, or just to have no choices out there besides adware, keep boycotting every developer who uses a subscription, regardless of how cheap it is.
If you want apps that are diligently maintained and which keep working forever, reward developers who produce apps with reasonable subscriptions. I have a password manager that's $19 a year and covers my whole family, and a podcast player that's $15. That password manager comes out to a nickel a day.
I wouldn't have enough time in the day (or month) to use 30 apps, or even 10, once you subtract all the first-party ones and ones that are just interfaces for things that are monetized separately (grocery store app, restaurant app, Uber, etc).
I have 3 paid subscription apps.[1] Total cost $43 a year. My only point was that if there's an app that is useful why shouldn't you pay a small amount per year that sustains it, guaranteeing that it gets good attention from a developer who is accountable not to their advertisers, but their users.
[1] Note: That doesn't count streaming services, but my family paid for cable 30 years ago and that was fine. It's entertainment.
I shouldn’t pay because I’ve already paid. Price updates for the same major version in. Let new sales be your incentive to keep it up-to-date. Let a new version I actually want be my incentive to spend more money.
Subscriptions for software that don’t offer an external service put all the incentives backwards strictly to the benefit of the developer and expense of the user.
There’s no question why it’s a great deal for the developer. But nothing you’ve said explains why any user should buy into this at all.
I'm not principally opposed to subscriptions, but subscribing to a camera app is absurd.
Your post prompted me to donate to KeepassXC, my subscriptionsless password manager, because I would be sad if that went away, and I would hate if the software landscape became even more a subscription hell than it already is.
I think the less frowned upon way to charge is to just do it once.
If the Apple store supports this, free trial + one time payment sounds like a good way. Don't optimize for freeloaders, as someone else said.
If the app relies only on iPhone hardware and/or is not a live service, an account/subscription should not be required. Even non-devs might justifiably ask "why do I need a subscription for a camera app".
Halide asks for a subscription. Not entirely sure why yet. Yes, it is more advanced than the normal app. Also slower and I haven’t noticed any changes or improvements in the last two years. Maybe support for new features in newer iPhones.
As for the subscription, there’s always been a pay-once option for major releases. You just miss out on a free trial, the beta program, and anything we might release with ongoing costs.
Halide's subscription system seems to have broken since late 2024/early 2025 — my v1 purchase with a different Apple ID from the one I'm usually logged in with (different country/region) wasn't being recognised.
When I emailed in, they blamed it on how the App Store mechanism changed.
Halide somehow is the only app that has this issue.
We switched to Apple's StoreKit 2 framework, which uses different internal plumbing. Not only is it the recommended way moving forward from Apple, but it improves the user experience for purchase management.
The issue is that, indeed, it actually validates that the App Store account currently logged in purchased the app. I believe this is intended behavior, as it closes a piracy loophole where you could log into the Apple ID of a friend, download all their paid apps, and then log in to a different account while retaining access.
If other apps don't run into this problem, it's possible they haven't moved on to StoreKit 2. Or the app has their own login independent of app subscription; setting aside the time it would take me to build that, I don't think most people are willing to create an account to try a camera app.
They offer both a subscription model and a lifetime purchase. Or that used to be the case, at least. But I agree that it feels like it's getting behind.
They just released a major update, but it's not something I would pay a subscription for. I paid the lifetime fee in it's early days, but that doesn't unlock the new updates sadly.
I use Analogue for day to day capture, and NoFusion and Moment apps for things I will want to edit later. All with one-time purchase. I don't mind paying for quality apps, but I do have subscription fatigue now.
There is still a lifetime purchase for the new version, IIRC. I can see it in the App Store IAP section. (Which is so useful! Lets me filter for apps that have a lifetime option at all.)
Also, I just checked, I purchased Mark II lifetime and got Mark III for free. It's only Mark I users that didn't get it.
Unfortunately it looks like lifetime users don't get access to the beta program for whatever reason. I guess they don't want feedback from those users.
I tried Analogue too, but I stopped using third-party camera apps altogether because they all seem to suffer from an issue where if you lock the phone too quickly after taking a photo, the photo is lost forever. I lost so many photos to this that I knew I took.
Apple limits TestFlight to 10,000 testers. Folks who are paying a recurring fee expect to see more frequent updates, so they get priority.
Halide shouldn't be afflicted by the lost photo issue you're talking about. Normally, if you close a lock-screen extension before a photo is written, it won't be in your library. This can be a problem when the user quickly smashes the capture button and your photo queue gets backed up.
Luckily, the unlocked app gets a chance later to access the content of lock-screen capture sessions. So our strategy in Halide is to write the intermediate files to disk as soon as you initiate a capture; this should take a split second. When we have uninterruptible time, later, we make sure the photo finished writing to your library, and if not, we try again.
However, Apple's documentation isn't clear if the OS will "wake-up" your main app to process unfinished photos, or if it relies on the user launching the app. I'll just say that I dog-food Halide every day by capturing photos of my toddler, and I can't remember the last time I lost a shot.
At this point, I don't remember if I was using Halide from the lock screen or not, but I lost tons of photos because apparently I turned the screen off before the photo finished saving to the library. Halide forgot about it, and even after reopening the app, it was gone forever. This would only seem to happen when I turned the screen off quickly after taking the photo.
These days, I use the regular Camera app because I need my damn photos to save. I loved Halide, but that bug made it too unreliable. I get very distressed by data loss and couldn't continue to risk it while trying to develop a way to work around it.
I don't think there's anything wrong with charging, even if you vibe coded it. You clearly put a lot of effort into the design and concept.
As I said in more detail below, on a free tier I expect to be able to at least try it out in a normal way. a monthly limit of exporting 3 pictures (eg to look at on my computer or TV) seems like something a normal person would hit in the first 30 minutes of just exploring what it does. Now, I noticed you run it this way for 14 days, but I gotta say that on first view this was massively outweighed by the 3/month limit.
subscription-wise, I just don't like them. If you are doing a ton of server-side processing, I'd rather pay on an as-needed basis. If not, I'd rather just Pay $19.99 (or whatever price you determine to be competitive in the market for photo apps). I see why subscription income would be nice to have for you, but for me it's a financial leaky faucet. In that case, I'd prefer to just go without because the app is a fun thing to have rather than a professional need.
It also bothered me that it was described as a 'reasonably priced' subscription. If I don't see a $ sign and a number, I reflexively classify it as a scam even though rationally I know you're just testing the waters. I close or dismiss 10 or 20 things a day after a cursory glance into whether they're worth my time or money: fear of being ripped off (FOBRO) outweighs the fear of missing out (FOMO).
Don’t listen to him, people like that will always complain, yet will never upgrade or pay for your product. He does not have a problem with your price but the mere fact that you are trying to sell something. Devs are like that.
Just differentiate signal from noise. Listen to your target audience not random internet comments
Wrong. I would definitely pay for this and was interested in it precisely because I just bought n iPhone. I spend $500-1000/year on software.
But if there's a free tier I want to try out normal use patterns over the course of a week or a month, and I prefer one-time payments or token purchases to subscriptions. I do the latter only for my IDEs, and still don't like it that much.
My objection was to the free tier only allowing one to export 3 images a month. That seems bizarre to me, since in course of trying something for the first time you might make 5, 10, or 20 images in an hour. If I'm running into a monthly limit in the first few minutes of using a tool, my immediate reaction is that it's something I can live without.
Nothing in the app is gated from day 1, you get 14 days of unlimited use before the choice of free vs paid is even presented, with no need to sign up for an official "free trial", so you have a good amount of time to make your mind up.
Nah man I’m not paying a subscription for a camera app that runs locally with zero need for cloud/servers/etc. beyond hosting their core product. I have paid as much as $50 for an app before (Artemis).
After I buy it I am zero burden to them beyond occasional updates, which I have very modest expectations of. They are far more likely to get my money if it’s one time. I can’t imagine paying a subscription for a physical camera, let alone a camera app on hardware I already paid a lot for
I wouldn't worry - there are some customers you don't want (and that's fine). Apps require a fair bit of upkeep and I imagine a camera app will need testing/modifying to ensure it works with the camera in every annual phone release. If you want to capture people who don't want a subscription add a lifetime plan 2-3x the annual price. Almost nobody will buy it. People complain about subscriptions but back in the day the number of people that complained when an app with 99¢ and not free was also staggering.
My suggestion is be generous and make a bit less money as the cost of making the world a kinder and more pleasant place. There's no rule that says you have to play ruthless capitalist.
I said: note that you are not obligated to maximize profit and you can give away more features for free and that it generally makes the world a kinder place to do so.
The point being that they have a choice. Contrary to what people are saying they are supposed to do, charge as much as possible, they can still choose to do something else. This is of course the normal mindset everywhere else, but HN seems to forget about it.
So what you're saying is that you prompted Claude to produce the app for you and now you're charging for it? A bold move, but I wouldn't expect much returns before there's completely free apps doing the same thing
If you have an enormous addressable market then it can pay to build awareness as quickly as possible. Having lots of enthusiastic users will do that. Having a useful free tier is a pretty uncontroversial way to get those users.
Plenty of apps do this - looking at the first browser tab I have open I see gmail which does exactly this.
For a pure client app like an iphone app, you don't have any real "per user" costs, so there are no concerns about going under from the costs of attempting this. It would be very different if you had to pay for server capacity.
It’s weird, because the center of the image will be more detailed, so how are they dealing with the “grid of pixels” that is on the display. Are they doubling up the wide angle.
“Easy-to-understand framing
The brackets over the viewfinder indicate the area covered by the more detailed lens. Frame your subject inside them to capture the best detail.“
Reminds me of the old 3d cameras that took two photos at once through 2 lenses (on film)
I'm scaling the wider 'outer' image using Core Graphics 'CGInterpolationQuality' to avoid blocky pixellation, then feathering the seam between the two lens outputs so the transition isn't jarring.
I didn't know about those Nishika stereo cameras, that looks incredible!
Phones can't fit a zoom lens with moving elements. The other cameras are just other prime lenses so you aren't restricted to having a single focal length all the time.
When you hit the little 0.5x, 1x, 4x buttons in the camera app you are switching between the physical cameras. Though Apple goes out of their way to obscure what is actually happening.
The obvious issue with the product here is that the telephoto lens will not cover the whole image that the 1x captured so only some portion of the center of the frame will be higher resolution.
Each camera has a different optical system with a different focal length range. This lets the camera cover everything from ultra wide angle to telescopic magnification while remaining thin enough to fit in a phone.
There's nothing to copy. Apple's iOS Camera app already uses multi-camera image fusion in many cases. This app builds on the Multi-Camera AVCapture feature that Apple opened up in iOS 13.
Apple has done this (multi-camera/spatial fusion) since 2016, in addition to multi-frame/temporal fusion. The OS decides whether these techniques are worthwhile for any given shot based on context.
Definitely not peak, my kid asked for a Rubik's Cube solver app which turned out to be subscription based, then wanted to tune her Ukelele with an app which turned out to be subscription based.
That's what makes me sad about the current Tetris game, on iOS.
One of my favorite games ever, and I'd gladly pay for an ad-free version, but they don't have it. I assume there's much more money to be made with ads, over subscriptions.
It's not that rare for games to offer a "remove ads" option for a few bucks. That model doesn't require a lot of extra "maintenance".
I think a few bucks for ad-free brings in more money for most developers, but that still pales in comparison to a recurring subscription model (or models where people keep spending in-app on consumables).
This is why some hardware is still supreme. I've had the same Korg chromatic tuner for 20 years and would not be in the least bit surprised if it goes for another 40.
This sort of nonsense is what I think will drive adoption of AI for personal apps. Tell it to create a ukulele tuning app and you get one without ads without subscription that you can make work exactly how you want. I wonder whether this is something that only privacy and tech oriented folk will do and care about our whether it will be adopted generally.
The source of this problem is that it costs $99/year + the churn of having to keep up with the latest ios api updates to have an app for iphones. Which kills the normal free software that would have filled this role. As well as the fact that the subscription apps can pay for adverts to sit at the top of the search results.
Once governments force Apple to allow sideloading we should get some kind of f-droid for ios which only lists open source user respecting apps.
There was some video on reddit that I saw the other day where a man struggled to take a photo with his camera app because it kept popping full screen ads in front of everything else.
There is Halide which I find completely uninteresting because I have a Sony A7iv. (Funny my latest piece of “gear” I am learning to use is a selfie stick because I can do stuff like https://mastodon.social/@UP8/tagged/selfie and I don’t see third party apps really improve on the official camera)
I'm confused. So this is just producing a single photo that is clearer in a middle rectangle and blurrier outside that rectangle?
Of course the extra detail in the middle is nicer, but won't the edge of the "detail rectangle" be extremely obvious and distracting? Like when you zoom into satellite view on Maps and it's clear that there's a blurry area and a sharp area?
I don't understand why you'd ever want these two things combined into a single image. I can understand why you'd want to snap photos with both lenses simultaneously as save them as separate photos, but I don't understand why you'd combine them.
> I don't understand why you'd ever want these two things combined into a single image.
An image with the FOV of the wide-angle camera but the quality of the main one in the center? Assuming the border interpolation works well (which tbf is probably hard for close objects), why would anyone not want this?
There are fashion subscriptions. Some people do not value being able to continually rewear clothes and would prefer to constantly having new clothes to show off.
That's absurd. I've gotten value from my toilet plunger for years. Let me start charging you a toilet plunger subscription just for privilege of using it when you please. That's your logic.
Recently, Samsung introduced the ISOCELL platform which allows to select the area which will be recorded at higher resolution compared to other regions.
There can be all sorts of different applications build around such as extracting higher resolution of text regions, etc [2].
Of course, the lens needs to support this resolution but I think that will be default in the mid-term future.
Pretty cool -- I built see ya' an app which allows you to connect N number of phones locally, and use one phone as the view finder + shutter, and the other(s) as the dedicated camera. I'm just using Apples native API, so it'll connect over bluetooth, wifi, direct, whatever pretty seamlessly. I don't collect any data, and it's 100% free.
That's super handy, thanks! I've been using one of those selfie monitoring screens and opening the camera to record video + turning on the flash, this app seems like a better way of accomplishing this
Apple’s MultipeerConnectivity framework -- phones discover and talk over local wifi / bluetooth via MCSession, MCNearbyServiceAdvertiser, and MCNearbyServiceBrowser in PeerSessionManager.
How can you in good conscience charge a subscription for this? It would be one thing if the app relied on infrastructure, but it's a one and done algorithm that's entirely local on device!
Subscriptions are charged because the developer needs to maintain the upkeep and cost of running the service, but that's not applicable here. It's capable of taking a million photographs fully offline, without any reliance on an online service.
Essentially you're saying your product is so superb that people should pay you indefinitely for the privilege of using it. Even though it costs you nothing to maintain, you somehow need people to perpetually pay you for a local, offline algorithm that you wrote one time. How gross, that's the definition of pointless greed.
Shame on you, honestly. This is exactly what's wrong with modern software nowadays. Just like Adobe and all these other companies, taking advantage of people to milk them dry forever. You'll lease a product, you won't have the right to own anything, and you'll be happy about it.
>It would be one thing if the app relied on infrastructure
Look into value based pricing. It's a mistake to charge based on how much something costs you to produce.
As an example, if I make an SEO tweak that makes a company an extra $10M in profit a year, should I charge for the hour of effort it took? Or should I charge differently?
I want to know what is possible if there were triple the number of cameras on the back of the phone and every single one fired on every photo. If they all focused at different points, the telephotos zoomed at different lengths etc., maybe throw some infrared cameras on there as well, what would be the results when combined?
There is a much better way of doing this which some professional cameras do called pixel shift. It shifts the sensor a tiny amount in between multiple exposures to compose in to an absurdly high resolution image. The downside is it only works on a tripod since you need the camera perfectly still.
The obvious issue with multiple cameras at different focal lengths is they won't all cover the frame of the widest one so only parts of the image will be sharper.
But if this matters to you, just get a full frame camera. Any 33MP full frame will blow away a 200MP phone camera in sharpness and detail.
I wasn't thinking so much about resolution, but rather all the other things it might allow. Re-focusing after taking it, for example. 3D by default, since the width of a phone is basically the distance between your eyes. A host of other things the much-more-high-powered CPU on the phone can do compared to a camera.
Very cool stuff, I've long thought there must be some fancy ways to get extra information for better image resolution by taking advantage of the other cameras.
That said, I must also say that most of the side-by-side comparison photos shown here are somewhat impressive, and in some cases, the photosynthesis one just looks worse to my untrained eye.
_______________
I'll choose to take this as evidence of the fact that you're tacking a very difficult problem, and you're also being honest in your comparisons and not cherry-picking too aggressively.
As dole alluded to below, I have been going back and forth in balancing the quality of the example pictures with the data load. I've pushed an update to the site now that weighs much more towards quality for this exact reason! But you're right, I don't want to hide the fact that not all results are perfect.
I think this is actually how oneplus phones have taken 'night' mode photos for a very long time in their default camera app, it takes multiple exposures and uses the movement sensor in the phone to pick several which were taken with the least hand jitter, and then stacks them into the final result.
I am co fused, 50% of photos look better in standard zoom and 50% of them look better woth photosynthesis. This is like an anti campaign for the app hinting "in the end it doesn't really matter"
I think this may be due to an issue I've had with loading the full res zoom images on the website, I've been going back and forth trying to balance the loading times and stress on the browser with clarity of the images. Working on a new idea now, so hopefully it'll give better demonstrations soon.
This might be a personal preference thing, but in every single example photo on that page, I significantly prefer the colours in the "standard zoom" version of the photo. I wonder if they can figure out how to do this fusion without losing that beautiful contrast the zoom lens brings to the table?
That's really interesting - the colour match attempts to find the best match between the two lens outputs, which frequently results in them 'meeting in the middle'. You can then manually adjust the output of each lens within the app's editing interface. I'll have a think about the weighting of the colour match.
Parallax error decreases significantly when lens are close enough and these are mm apart. They are close enough that you can probably just play a perspective trick and hide any artifacts.
This was actually a purported feature of the Pixel 3 camera. Google said it would be constantly taking photos and the different information captured as your hand moved slightly could be used to create higher information density photos. It didn't work very well at that point but the idea was cool!
I believe that's a similar idea to Apple's Deep Fusion which also takes multiple frames from the same lens then intelligently combines them for higher detail. As ipsum2 said below, that's different to Photosynthesis, which captures from different lenses simultaneously.
very cool app, a few questions: why does the color "temp" of the image change between traditional iphone photography vs your app? it appears to both warm and cool the images. Also why is the contrast decreased, specifically in the library/book store example?
I like the idea of this app and the website is well done. Subscription isn't for me, but for folks who take a lot of photos and need this sort of thing, I can see it. Free tier could offer a few more photos per month.
All 3 is in the app! It's a much harder challenge to deal with the parallax and other artefacts that come up from combining 3 lenses, so that particular feature is launching in beta.
My hesitations on this are it stores data in a proprietary format that I may not be able to export to another common format if the product disappears in a few years.
For something personal like photos and the memories they capture, that's not ideal for me.
While the app is still with us, I'm not sure how much it will cost me to export to my photos to my photo library each month.
There is zero lock-in with the files being saved - you can export from the app in HEIC/PNG/JPEG as well as PSD and spatial/SBS 3D. The format the website calls the 'Photosynthesis' file is an HEIC so even if you export that you can still access the data outside of the app.
Unlimited exports of the composite images are part of the subscription (with an option to automatically export to Photos.app and/or a folder of your choosing), but the free tier still offers unlimited saving of the constituent images e.g. the wide & tele shots, just not the composite.
This appears to use a naïve masking approach (using ML to find the edges of the mask) which seems to suffer from slight uncorrected differences in lens distortion. There's a fairly obvious feathering around the edges of the detailed area, objects shift quite dramatically, and overall I feel like I'd do a better job of this manually. It is a cool idea, but flawed execution. I would prefer something like using ML to generate a displacement map between the wide angle and the narrow angle parts. That way you can map the higher details down faithfully without having to feather the edges nearly as much or compute any mask. That would also solve parallax which I see also looks unaccounted for.
This whole thing feels wrong. OP should be working for a phone manufacturer, not trying to sell this as a subscription. How much is it worth to be able to squeeze a little more visual clarity out of my phone? Maybe $20 maximum? And I feel like I’m on the generous side of the population here. Most people will say $0. But if you’re inside of Apple and you can tell them you can add an average of $1 of perceived value to each of their millions of phones sold each year they’ll be over the moon and you can get a fat salary.
"There is a crazy amount of image processing going on behind the scenes in each smartphone"
I bought the Pixel 10 because it said it had great zooming capabilities. After 5X (that means 10X), it's completely stupid. Basically it takes a very blurred photo and then tries to reconstruct it with AI. The final results are completely awful and really distant from reality.
Any advice in how to improve that?
Edited to add: I have a pixel 10 pro which has a better zoom lens, so I could be having a different experience than you...
Makes for a fine image if "looking good" is the objective (which it often is), but I wouldn't trust it to disambiguate anything uncertain.
So the ENHANCE is no longer just some lazy movie writing!
The biggest of the "sharpening with AI" models, if you let 'em go, they'll turn you into a celebrity on accident.
If you go to the Topaz AI forums on Facebook, you'll see examples of where the AI sharpening tool went off the rails and turned a blurry photo of someone (typically the user who bought the software, who is trying to clean up their own photos) into whichever celebrity that is in the AI model who resembles them.
IE, it might turn a photo of YOU into a photo of Robert Downey Jr.
Also wonder how how long until photos are no longer court-admissible evidence because they get overwhelmed with the burden of the amount (and the cost) of the "non-AI" certification?
The only solution I see is some kind of hardware-linked signature showing that the image was produced at a certain time, by a certain device. In theory, you could make this signature somewhat “provable” and anchored to a specific time by combining something like 1) the latest Bitcoin block hash, and 2) a blockchain anchor, thereby proving that the photo was taken within a certain time widow after the hash was known and before the anchor was published. But even that arrangement is highly susceptible to hardware attacks.
Because of the limitations of capturing multiple lenses at once through isVirtualDeviceConstituentPhotoDeliveryEnabled, there is a second capture mode in the app for 'Quality' which takes a simultaneous capture then takes sequential shots from each lens which do benefit from Deep Fusion, then uses those for the stitch (as long as the Deep Fusion images outperform the simultaneous capture results). That's also what I do for our Night mode.
The result when done outdoors (like, standing in a dark forest at midnight) will be a photo where you can actually see what's around you, and details show up as if it was a brightly full moon lit night.
The math is surely more complex than aligning same-lens photography even when you consider the change in angle and perspective between two shots from the same lens.
https://www.google.com/search?client=firefox-b-d&q=ARGUS+pho...
The reborn Nokia/HMD was also doing multi-sensor image stacking back in 2019 on the Nokia 9 Pureview.
Google has some great blogs about their camera technology https://research.google/blog/night-sight-seeing-in-the-dark-...
From the authors of Halide.
Edit: actually I can't seem to find the setting that aligns them. I seem to remember it being able to do that but maybe it doesn't... which would be disappointing...
I agree, and I built it!
The app launched in 2019. Ideally I would have said ML, but it felt like AI had more recognition among non-technical users.
If I launched it in 2026, it would 100% say "ML" not only because it's more technically accurate, but to make it abundantly clear it doesn't generate slop.
Since at least the iPhone 12, holding the phone still and letting scene sit for a few seconds will result in a sharper photo. I’m not sure if it’s a subtle version focus stacking or a sharpening algorithm, but it’s definitely there.
On my 16e, immediately looking at a photo just taken can result in the image noticeably sharpening after a second or 2, so this may be a post processing step as well.
I’m guessing it has to do with how intensely focused / scared my brain was with the little guy
https://apps.apple.com/us/app/twincam/id6448645623 https://play.google.com/store/apps/details?id=org.evergreenl...
Except for the "have full network access" permission according to the Google Play Store.
The fact that they have to resort to manipulation to sell their product tells me that they are not trustworthy and that their product is probably underwhelming.
Not to mention the developer account subscription is $99/year
In general, when I buy something I want to pay for it once and then have it. I don't want to rent or lease it, even if it's consumable. When I eat a restaurant I I pay for the meal when it's over; if it was delicious I might come back again. Even if I like it so much that I eat there every week, that doesn't mean I want a weekly subscription.
An engineer with an app can come to work 365 days a year, fix bugs, add nice new features, unbreak the app every time iOS updates, and, though you use the app every day, they can't count on you to give them another $5 every year - or ever again - unless you enter into a subscription.
This isn't to say you have some obligation to do a subscription to any app you don't think is worth it, but for apps from non-scam developers, they're usually like $20 or less a year - about a nickel a day. A nickel is 3¢ in year-2000 dollars btw.
It's on the developer to prove to you that the app is worth paying a nickel a day to have! But ruling it out just because we wish it didn't have to be, well, that just rewards the developers who monetize exclusively with ads or sell their 'free' apps to sketchy operators.
I'd like it if Uber was free or just cost a buck a ride flat rate, but I know that anyone willing to give me a ride on terms like that is probably looking to rob me.
After a year, I don't think anyone is bothered if an app becomes unsupported for whatever reason. Usually what happens is the opposite - developer unnecessarily cripples an existing, perfectly working app, to try to milk some more revenue out of it.
This is an especially moot point now that most platform API upgrades are $1 of LLM work away.
I was just listing one more thing a developer who wasn't slacking might spend his time doing, that's all.
> Keeping the app compatible with new OS releases is necessary to keep sales going.
Relying on constant sales to new users sounds like a pyramid scheme. Software licenses don't wear out like shoes or become consumed like butter, with happy customers returning to buy more. Eventually, most of the people that need most apps have bought it and sales don't "keep going" more than a trickle, except for apps that are such mainstream hits that your new users are just "everyone who became old enough this month to get their first phone." And because the App Store has ruined organic discovery, paid apps rely almost exclusively on paying for installs either via Apple's ads or elsewhere. So, that eats a good part of each new sale's revenue right away.
Check the iOS top charts right now. For paid apps, the top-selling app is Shadowrocket, a rule-based proxy utility. How long until all developers who want a rule-based proxy utility have already paid the $3? If 100,000 developers buy that app, then that developer nets $210,000 pre-income-tax. About on par with a good corporate SWE job outside of FAANG. But that will slow down. There just aren't that many people who are looking for that. #2 is just a client of a subscription service for businesses. #3 is AnkiMobile Flashcards at $25. See, at that price I agree it can afford to never charge again. #4 is an ephemeral app for some art event in Portland so it doesn't need to be sustained. #5 is Procreate Pocket. I guess there are enough new aspiring artists appearing every day who can afford these apps (I think it's $13 for iPad).
> After a year, I don't think anyone is bothered if an app becomes unsupported for whatever reason.
Okay, so subscribe to the apps you use, and then immediately go in and turn off renewal in Settings -> (your Apple ID) -> Subscriptions. There. You now have a one-time purchase of an app which will stop working in a year - just like apps that have no recurring revenue stream do.
> This is an especially moot point now that most platform API upgrades are $1 of LLM work away.
I don't think you are a developer of serious iOS apps. Just the visual changes, that users expect apps to go along with, require major redesigns. People don't buy apps that look like they were designed in 2019.
It's not the amount of the payment. It's the subscription model I can't stand. You're correct that I might use an app I like every day. But the marginal cost to the developer of me using it every day is $0. Rather than belabor the restaurant example , consider a book or a music CD. Writing books or recording music is generally a slow and difficult process, it takes months to produce one that might be read in a weekend. But if you buy a book, you can read or refer to it every day without paying again, or you cna listen to your favorite songs as often as you like by playing the CD. Nowadays many people prefer to stream music, but I think when people buy a book (even an e-book), they consider that it's their copy to read as often as they want...
...or not. If I buy a book and I don't like it, or later I find another book that I turn out to prefer to the first one, I can just not read it again. I don't have to cancel a subscription for the book.
It aligns your incentives with the developer very well. They really want you to not cancel your subscription after only paying the first year's payment (when you may not have even paid back the customer acquisition cost!), and you want the app to be high quality and well-maintained. If the developer doesn't meet your bar for that, you cancel the subscription with 4 taps and they lose future income. That incentive to please customers after the sale just doesn't exist in a pay-once app world (except in tiny niches of old-school developers, like the Panics of the world, whom I do greatly respect).
Besides the incentives, it also gives you a chance to, after that one-year $7 spend, re-evaluate "do I even use this anymore?" If you paid for a guitar tuning app and you stopped playing guitar, you can just cancel the subscription, even before you've paid the amount that they'd have priced it for one-time-purchase. There is upside for the consumer in the apps that either let you down, or that you simply realized you no longer need, and it lowers the risk bar to try an app that you aren't sure about.
I get that if you do end up using such an app for the next 15 years, yes you'll probably pay somewhat more than any price you'd have considered paying one-off, but it also probably means that app (an app you use often for decades) couldn't have been sustained for all that time with only new customer installs paying the bills.
> if you buy a book, you can read or refer to it every day without paying again, or you cna listen to your favorite songs as often as you like by playing the CD.
We agree that this is all very great. And since the music or book you buy carries zero support burden of any kind from the artist it's a pretty great model - after their album launches the artist can devote 100% of their bandwidth to producing new music, or they can tour to get recurring income out of the same music, or a mix of the two.
If you paid for it once and only got to keep the version of it as of when you paid for it, in a couple years the platform would remove your ability to use it.
So, in the old days, you paid often $50-500 for a piece of software and the developer would usually have zero burden to update the software for you. By the time the OS completely broke it, it would have been 5+ years later. All that time, the developer was freed up to build and sell whole other applications, or, to innovate new and compelling features to get you to pay the upgrade price to get a new version.
Today that developer would have to do 5 major updates with breaking API changes, and probably at least 1 full visual refresh just to keep up with Apple's changing design whims, just for that one app to not be bricked. They have less bandwidth then to build more apps, since each app carries its own annual burden of churn.
If you had customers buying last year, it’s likely you’ll have even more customers buying next year. If you stop maintaining your app, that stream of new sales almost immediately dries up.
Offline mobile apps which charge a subscription are a very silly fad to me. The few that get away with it are being steadily edged out by someone else who wants to eat their lunch.
I love the OP’s idea and absolutely see the use case. I also think it’s very promptable. My unsolicited advice is to strike while the iron’s hot at $0.99, because I’d be very skeptical if they’ll attract enough subscribers before getting starved out by copycats.
https://apps.apple.com/us/app/a-dark-room/id736683061
Giving this advice to developers today is frankly absurd career advice.
1. Few apps can achieve the scale needed for a one-time fee to be sustaining for the app - most apps appeal to a finite set of people, and eventually most who are in your target market (and who are willing to spend actual upfront money), have bought the app.
2. An entire generation has grown up that has never paid more than maybe 99 cents for software, and most refuse to even pay that - they're used to adware. You can't price an "app" at $75 and expect it to be bought by essentially anyone. While adware can actually be a very financially viable route, many developers hate ads and want nothing to do with this model.
3. Unlike the multiple years of stability of old desktop operating systems, platform owners today think nothing of breaking even a plurality of apps with any major OS version - and for some insane reason they also think a new "major version" ought to come out annually.
If you want apps that cease getting updates after a few months and age very poorly, or just to have no choices out there besides adware, keep boycotting every developer who uses a subscription, regardless of how cheap it is.
If you want apps that are diligently maintained and which keep working forever, reward developers who produce apps with reasonable subscriptions. I have a password manager that's $19 a year and covers my whole family, and a podcast player that's $15. That password manager comes out to a nickel a day.
I pay exactly zero a month in subscriptions.
I wouldn't have enough time in the day (or month) to use 30 apps, or even 10, once you subtract all the first-party ones and ones that are just interfaces for things that are monetized separately (grocery store app, restaurant app, Uber, etc).
I have 3 paid subscription apps.[1] Total cost $43 a year. My only point was that if there's an app that is useful why shouldn't you pay a small amount per year that sustains it, guaranteeing that it gets good attention from a developer who is accountable not to their advertisers, but their users.
[1] Note: That doesn't count streaming services, but my family paid for cable 30 years ago and that was fine. It's entertainment.
Subscriptions for software that don’t offer an external service put all the incentives backwards strictly to the benefit of the developer and expense of the user.
There’s no question why it’s a great deal for the developer. But nothing you’ve said explains why any user should buy into this at all.
Your post prompted me to donate to KeepassXC, my subscriptionsless password manager, because I would be sad if that went away, and I would hate if the software landscape became even more a subscription hell than it already is.
Pedants corner:
>most apps appeal to a finite set of people
The set of people is finite.
If the Apple store supports this, free trial + one time payment sounds like a good way. Don't optimize for freeloaders, as someone else said.
If the app relies only on iPhone hardware and/or is not a live service, an account/subscription should not be required. Even non-devs might justifiably ask "why do I need a subscription for a camera app".
https://www.lux.camera/halide-mark-iii/
As for the subscription, there’s always been a pay-once option for major releases. You just miss out on a free trial, the beta program, and anything we might release with ongoing costs.
When I emailed in, they blamed it on how the App Store mechanism changed.
Halide somehow is the only app that has this issue.
The issue is that, indeed, it actually validates that the App Store account currently logged in purchased the app. I believe this is intended behavior, as it closes a piracy loophole where you could log into the Apple ID of a friend, download all their paid apps, and then log in to a different account while retaining access.
If other apps don't run into this problem, it's possible they haven't moved on to StoreKit 2. Or the app has their own login independent of app subscription; setting aside the time it would take me to build that, I don't think most people are willing to create an account to try a camera app.
I use Analogue for day to day capture, and NoFusion and Moment apps for things I will want to edit later. All with one-time purchase. I don't mind paying for quality apps, but I do have subscription fatigue now.
Might check it out. Thanks for letting me know. But really been enjoying Analogue lately.
Unfortunately it looks like lifetime users don't get access to the beta program for whatever reason. I guess they don't want feedback from those users.
I tried Analogue too, but I stopped using third-party camera apps altogether because they all seem to suffer from an issue where if you lock the phone too quickly after taking a photo, the photo is lost forever. I lost so many photos to this that I knew I took.
Halide shouldn't be afflicted by the lost photo issue you're talking about. Normally, if you close a lock-screen extension before a photo is written, it won't be in your library. This can be a problem when the user quickly smashes the capture button and your photo queue gets backed up.
Luckily, the unlocked app gets a chance later to access the content of lock-screen capture sessions. So our strategy in Halide is to write the intermediate files to disk as soon as you initiate a capture; this should take a split second. When we have uninterruptible time, later, we make sure the photo finished writing to your library, and if not, we try again.
However, Apple's documentation isn't clear if the OS will "wake-up" your main app to process unfinished photos, or if it relies on the user launching the app. I'll just say that I dog-food Halide every day by capturing photos of my toddler, and I can't remember the last time I lost a shot.
These days, I use the regular Camera app because I need my damn photos to save. I loved Halide, but that bug made it too unreliable. I get very distressed by data loss and couldn't continue to risk it while trying to develop a way to work around it.
As I said in more detail below, on a free tier I expect to be able to at least try it out in a normal way. a monthly limit of exporting 3 pictures (eg to look at on my computer or TV) seems like something a normal person would hit in the first 30 minutes of just exploring what it does. Now, I noticed you run it this way for 14 days, but I gotta say that on first view this was massively outweighed by the 3/month limit.
subscription-wise, I just don't like them. If you are doing a ton of server-side processing, I'd rather pay on an as-needed basis. If not, I'd rather just Pay $19.99 (or whatever price you determine to be competitive in the market for photo apps). I see why subscription income would be nice to have for you, but for me it's a financial leaky faucet. In that case, I'd prefer to just go without because the app is a fun thing to have rather than a professional need.
It also bothered me that it was described as a 'reasonably priced' subscription. If I don't see a $ sign and a number, I reflexively classify it as a scam even though rationally I know you're just testing the waters. I close or dismiss 10 or 20 things a day after a cursory glance into whether they're worth my time or money: fear of being ripped off (FOBRO) outweighs the fear of missing out (FOMO).
Just differentiate signal from noise. Listen to your target audience not random internet comments
But if there's a free tier I want to try out normal use patterns over the course of a week or a month, and I prefer one-time payments or token purchases to subscriptions. I do the latter only for my IDEs, and still don't like it that much.
My objection was to the free tier only allowing one to export 3 images a month. That seems bizarre to me, since in course of trying something for the first time you might make 5, 10, or 20 images in an hour. If I'm running into a monthly limit in the first few minutes of using a tool, my immediate reaction is that it's something I can live without.
I am also considering a lifetime unlock option.
After I buy it I am zero burden to them beyond occasional updates, which I have very modest expectations of. They are far more likely to get my money if it’s one time. I can’t imagine paying a subscription for a physical camera, let alone a camera app on hardware I already paid a lot for
I said: note that you are not obligated to maximize profit and you can give away more features for free and that it generally makes the world a kinder place to do so.
The point being that they have a choice. Contrary to what people are saying they are supposed to do, charge as much as possible, they can still choose to do something else. This is of course the normal mindset everywhere else, but HN seems to forget about it.
Plenty of apps do this - looking at the first browser tab I have open I see gmail which does exactly this.
For a pure client app like an iphone app, you don't have any real "per user" costs, so there are no concerns about going under from the costs of attempting this. It would be very different if you had to pay for server capacity.
“Easy-to-understand framing The brackets over the viewfinder indicate the area covered by the more detailed lens. Frame your subject inside them to capture the best detail.“
Reminds me of the old 3d cameras that took two photos at once through 2 lenses (on film)
https://www.ebay.com/itm/206409326865?chn=ps&_trkparms=ispr%...
I didn't know about those Nishika stereo cameras, that looks incredible!
When you hit the little 0.5x, 1x, 4x buttons in the camera app you are switching between the physical cameras. Though Apple goes out of their way to obscure what is actually happening.
The obvious issue with the product here is that the telephoto lens will not cover the whole image that the 1x captured so only some portion of the center of the frame will be higher resolution.
https://developer.apple.com/videos/play/wwdc2019/249/
https://developer.apple.com/documentation/avfoundation/avcap...
https://www.theguardian.com/technology/2014/jan/06/apple-buy...
https://en.wikipedia.org/wiki/Concert_pitch
One of my favorite games ever, and I'd gladly pay for an ad-free version, but they don't have it. I assume there's much more money to be made with ads, over subscriptions.
I think a few bucks for ad-free brings in more money for most developers, but that still pales in comparison to a recurring subscription model (or models where people keep spending in-app on consumables).
Once governments force Apple to allow sideloading we should get some kind of f-droid for ios which only lists open source user respecting apps.
Of course the extra detail in the middle is nicer, but won't the edge of the "detail rectangle" be extremely obvious and distracting? Like when you zoom into satellite view on Maps and it's clear that there's a blurry area and a sharp area?
I don't understand why you'd ever want these two things combined into a single image. I can understand why you'd want to snap photos with both lenses simultaneously as save them as separate photos, but I don't understand why you'd combine them.
An image with the FOV of the wide-angle camera but the quality of the main one in the center? Assuming the border interpolation works well (which tbf is probably hard for close objects), why would anyone not want this?
Your own eyes work that way, so you tell me.
Yeah that looks to be the case. Not sure what use case this solves with that 'limitation'. I don't think photographers would particularly like this.
No we really don’t.
And Nike for the shoes on my feet.
Recently, Samsung introduced the ISOCELL platform which allows to select the area which will be recorded at higher resolution compared to other regions.
There can be all sorts of different applications build around such as extracting higher resolution of text regions, etc [2].
Of course, the lens needs to support this resolution but I think that will be default in the mid-term future.
[1]: https://en.wikipedia.org/wiki/Foveated_imaging
[2]: https://dl.acm.org/doi/10.1145/3799902.3811218
https://apps.apple.com/us/app/see-ya/id6792367530
That seems super cool! You could almost strap an iPhone to the back of your phone and see yourself for recordings.
https://github.com/0Itsuki0/SwiftUI_P2PWithNetwork
I also have an app that uses device camera and I don’t write about it in mostly unrelated submissions.
On my phone, at least, I had to pintch-to-zoom to 2-3X to see the difference.
And at that size, the “synthesized” version looks much sharper.
You might need more cropping for the mobile version. At 1X I couldn’t tell them apart.
Haven’t checked the desktop version yet
Subscriptions are charged because the developer needs to maintain the upkeep and cost of running the service, but that's not applicable here. It's capable of taking a million photographs fully offline, without any reliance on an online service.
Essentially you're saying your product is so superb that people should pay you indefinitely for the privilege of using it. Even though it costs you nothing to maintain, you somehow need people to perpetually pay you for a local, offline algorithm that you wrote one time. How gross, that's the definition of pointless greed.
Shame on you, honestly. This is exactly what's wrong with modern software nowadays. Just like Adobe and all these other companies, taking advantage of people to milk them dry forever. You'll lease a product, you won't have the right to own anything, and you'll be happy about it.
Look into value based pricing. It's a mistake to charge based on how much something costs you to produce.
As an example, if I make an SEO tweak that makes a company an extra $10M in profit a year, should I charge for the hour of effort it took? Or should I charge differently?
The obvious issue with multiple cameras at different focal lengths is they won't all cover the frame of the widest one so only parts of the image will be sharper.
But if this matters to you, just get a full frame camera. Any 33MP full frame will blow away a 200MP phone camera in sharpness and detail.
Good review: https://www.youtube.com/watch?v=j3uUozW4zHc
That said, I must also say that most of the side-by-side comparison photos shown here are somewhat impressive, and in some cases, the photosynthesis one just looks worse to my untrained eye.
_______________
I'll choose to take this as evidence of the fact that you're tacking a very difficult problem, and you're also being honest in your comparisons and not cherry-picking too aggressively.
Lytro, Inc. was an American company founded in 2006 by Ren Ng which developed some of the first commercially available light-field cameras.
https://en.wikipedia.org/wiki/Lytro
For something personal like photos and the memories they capture, that's not ideal for me.
While the app is still with us, I'm not sure how much it will cost me to export to my photos to my photo library each month.
Unlimited exports of the composite images are part of the subscription (with an option to automatically export to Photos.app and/or a folder of your choosing), but the free tier still offers unlimited saving of the constituent images e.g. the wide & tele shots, just not the composite.
What do the multiple lenses do then, if not this? Like,I presumed that was the point.
Are they LITERALLY just decoration for me to make fun of?
Many phones already use information from both cameras, too.
Android phones have multiple cameras too.
I immediately signed up. (And offered to help bring users to this thing.)