That's not just interruptions. It's the notifications bar itself.
I noticed this only recently - I switched the default phone launcher to a scifi theme built on Total Launcher (there's legit personal research project reasons behind that, it's not just to look cool!) and after few days (and a bunch of missed messages), I realized my life seems suspiciously light in interruptions and random events. It took me a few more moments to pin-point the reason: the theme hid the notification bar entirely. It was still there, ready to pull down and expand with a gesture or a button tap - but that top line with icons was not visible (and through the stroke of luck, I misconfigured something in another experiment and had no notification indicators on the lock screen, either).
Not having notification indicators visible on any surface is really all it took - and conversely, this means that just having them there created the majority of the burden for me. I thought I successfully solved the distraction problem by silencing or eliminating ads and useless notifications, but now I know that even the important ones aren't really that important for the burden their very existence creates.
Android modes provide control over notification display.
Modes control which people and apps can trigger a sound/vibration, but also offer the option to hide the silenced notifications from the status bar, pull-down shade, and dots on app icons. I hide them from the status bar, but not the pull-down shade so that I can manually check if I want to, but don't see them at a glance.
I'm not a heavy user of this feature though; I mostly don't install apps that have spammy notifications.
Right. I'm saying that living for a week without any notification bar at all made me realize that even my usual well-curated notification bar is impacting me much more than I realized.
I imagine usage patterns vary greatly. For me, most of the time, I have it set to only allow messages from contacts, and I usually handle those immediately.
You can always hold an accelerometer in your hand. If you did so now, assuming you're on Earth's surface, it'd register approximately 9.8m/s/s pointing in the upward direction.
You could also perform one of many historical experiments, such as dropping an object from an elevated height with careful timing, or rolling a round ball down a gently sloped track, and so on.
Or, just don’t play the game. I don’t mean to be flippant, but why waste time on software employing shoddy practices? Wordle and Apple’s mini crossword-minis are sufficiently stimulating and quick.
My tolerance for software like that is very limited. It’s almost an immediate long-press and uninstall.
Respectfully, if
I may offer constructive criticism, I’d hope this isn’t how you communicate to software developers, customers, prospects, or fellow entrepreneurs.
To be direct, this reads like a fluff comment written by AI with an emphasis on probability and metrics. P(that) || that.
I’ve written software used by a local real estate company to the Mars Perseverance rover. AI is a phenomenally useful tool. But be weary of preposterous claims.
I'll take you at your word regarding respectfully. That was an off the cuff attempt to explain the real levers that control the viability of agents under particular circumstances. The target market wasn't your average business potato but someone who might care about a hand waived "order approximate" estimator kind of like big-O notation, which is equally hand waivey.
Given that, if you want to revisit your comment in a constructive way rather than doing an empty drive by, I'll read your words with an open mind.
There are many things wrong with this. I have an iPhone 17 Pro Max and use it to capture HEIF 48 and ProRAW images for Lightroom. There’s no doubt of the extraordinary capabilities of modern phone cameras. And there are camera applications that give you a sense of the sensor data captured, which only further illustrates the dazzling wizardly between sensor capture vs the image seen by laypeople.
That said, there is literally no comparison between the iPhone camera and the RAW photos captured on a modern full-frame mirrorless camera like my Nikon Z6III or Z9. I can’t mount a 180-600mm telephoto lens to an iPhone, or a 24-120mm, or use a teleconverter. Nor can I instantly swing an iPhone and capture a bird or aircraft flying by at high speed and instantly lock and track focus in 3D, capture 30 RAW images per second at 45MP (or 120 JPEGs per second), all while controlling aperture, shutter speed and ISO.
Physics is a thing. The large sensor size and lenses (that can make a Mac Studio seem cheap by comparison) serve a purpose. Try capturing even a remotely similar image on an iPhone in low light, and especially RAW, and you’ll be sitting there waiting seconds or more for a single image. Professional lenses can easily contain 25 individual lens elements that move in conjunction as groups for autofocus, zoom, motion stabilization, etc. They’re state-of-the-art modern marvels that make an iPhone’s subject detection pale by compare. Examples:
I can lock on immediately to a small bird’s eye 300 feet away with a square tracking the tiny eye precisely, and continue tracking. The same applies to pets, people, vehicles, and more with AI detection.
You can handhold a low-light shot at 1/15s to capture a waterfall with motion blur and continue shooting, with the camera optimizing the stabilization around the focus point—that’s the sensor and lens working in conjunction for real-time stabilization for standard shots, or “sports mode” for rapidly panning horizontally or vertically.
There’s a reason pro-grade cameras exist and people use them. See Simon D’entrement, Steve Perry, and many others on YouTube for examples.
For most people, it doesn’t matter. They can happily shoot still images and even amazingly high-quality video these days. But dismissing the differences is wildly misleading. These cameras require memory cards that cost half as much or more than the latest iPhone, and for good reason [1].
With everything, there are
trade offs. An iPhone fits in my pocket. A Nikon Z8 and 800mm lens and associated gear is a beast. Different tools, different job.
You are totally missing my point and talking past me. I have a Nikon Z8! I know what it is capable of!
The point I'm trying to make is that the RAW images coming out of a modern full-frame camera get very "light" processing in a typical workflow (i.e.: Adobe Lightroom), little more than debayering before all further treatment is in ordinary RGB space.
Modern mobile phones have sensors with just as many megapixels, capturing a volume of raw data (measured in 'bits') that is essentially identical to a high-end full-frame sensor!
The difference is that mobile phones capture and digitally merge multiple frames captured in a sequence to widen the HDR dynamic range and reduce noise. They can even merge images taken from slightly different perspectives or with moving objects. They also apply tricks like debayering that is aware of pixel-level sensor characteristics and is tuned to the specific make and model instead of shared across all cameras ever made, which is typical of something like Lightroom, Darktable, or whatever.
If I capture a 20 fps burst with a Nikon Z series camera... I can pick one. That's about the only operation I can do with those images! Why can't I merge multiple exposures with motion compensation to get an effective 10 ISO instead of 64, but without the blur from camera motion?
None of this has anything to do with lenses, auto-focus, etc...
I'm talking about applying "modern GPU" levels of computer power to the raw bits coming off a bayer sensor, whether that's in a phone or a camera. The phone can do it! Why can't Lightroom!?
> I have a Nikon Z8! I know what it is capable of!
It seems to me you underestimate the amount of work your camera is already doing. I feel like you overestimate the raw quality of a mobile camera as well.
> Modern mobile phones have sensors with just as many megapixels, capturing a volume of raw data (measured in 'bits') that is essentially identical to a high-end full-frame sensor!
There may be the same amount of bits but that doesn't mean that it captures the same quality of signal. It's like saying that a higher amount of bits on a ADC correspond to a better quality signal on the line, it just isn't true. Megapixels are overhyped, resolution isn't everything for picture quality.
> The phone can do it! Why can't Lightroom!?
Be the change you want to see, if the features that you want are not in Lightroom write a tool to implement it (or add the features to a tool like ffmpeg). The features you are talking about are in just software after capture so it should be possible from the camera's raw.
Perhaps you would be better of buying a high quality point and shoot camera or just using your phone instead of a semi professional full-frame camera for your purpose. With a DSLR you have options how to process, if that means in your "typical workflow" light processing then that's up to you. perhaps If you want to point shoot, instagram you indeed don't want to spend time processing in Lightroom and that's fine.
It feels like you are complaining about how your expensive pickup can't fit your family and suitcases when going on holiday like the neighbors SUV even though they have the same amount of horsepower and are build on the same chassis. They are obviously build for different purposes.
They’re known as DNs, or digital numbers. Thom Hogan’s eBooks do a phenomenal job of explaining the intricacies of camera sensors, their architecture, processing to JPEGs, and pretty much every aspect of capturing good photos.
The books, while geared toward Nikon cameras, are generally applicable. And packed with high-quality illustrations and an almost obsessive uber-nerd level of detail. He’s very much an engineer and photographer. When he says “complete guide”, he means it.
The section on image sensors, read-outs,
and ISO/dual gain/S&R, etc. is particularly interesting—-and should be baseline knowledge for anyone who’s seriously interested in photography.
To be clear, they default to JPEG for the image preview on the monitor (LCD screen). Whenever viewing an image on a professional camera, you’re always seeing the resulting JPEG image.
The underlying data is always captured as a RAW file, and only discarded if you’ve configured the camera to only store the JPEG image (discarding the original RAW file after processing).
> Whenever viewing an image on a professional camera
Viewing any preview image on any camera implies a debayered version: who says is it JPEG-encoded - why would it need to be? Every time I browse my SD card full of persisted RAWs, is the camera unnecessarily converting to JPEG just to convert it back to bitmap display data?
> The underlying data is always captured as a RAW file, and only discarded if you’ve configured the camera to only store the JPEG image (discarding the original RAW file after processing).
Retaining only JPEG is the default configuration on all current-generation Sony and Canon mirrorless cameras: you have to go out of your way to persist RAW.
I’ve submitted multiple bug reports over the years using the Feedback app. And, to my surprise, not only did I receive a detailed response within a month or so, the issues were resolved.
reply