XPost: misc.phone.mobile.iphone
From: mariasophia@comprehension.com
Tyrone wrote:
> On Jan 2, 2026 at 8:00:41 PM EST, "Maria Sophia"
> wrote:
>
>> What are technical restrictions preventing useful apps on iOS?
>
> Nothing. I have loads of useful apps on my iPhones and iPads. Are you saying
> you have actually logged in to one of your alleged iOS devices, gone to the
> App Store and found nothing useful?
>
> Uh huh. Sure.
>
> But if they violate security by running random shell scripts - or other
absurd
> shit that apps have no business doing - then they will not work. They won't
> even make it into the App Store. And since loading from random websites is
not
> allowed - DING DING DING - iOS is more secure than Android.
>
> AGAIN, iOS is all about security. So we don't need the "secure browsers" that
> Android and Windows need.
>
> But hey, keep up the good work by asking ridiculous, easy-to-answer
questions.
> Questions that have already been answered many times.
>
> Any new insights on "crappy batteries" you would like to share? Any questions
> on how to move files back and forth between Windows and iOS?
Hi Tyrone,
Happy New Year!
You are responding to a question which is not asked in this technical
thread as I certainly did not claim that iOS has no useful apps.
I simply asked a purely technical question about categories of app
functionality that are possible on all other common consumer operating
systems but not on iOS due to iOS' innate baked-in architectural
restrictions on what iOS apps are allowed, by Apple to do.
Those restrictions aren't due to the Apple hardware.
But to the Apple decisions to not allow this functionality on iOS.
(Yet, it's on all other operating systems, including macOS in most cases.)
As to your personal feelings, whether a person finds iOS "useful" is
subjective. However, the restrictions themselves are objective and well
documented by Apple.
For example:
A. iOS does not allow arbitrary background daemons. Only short,
system-managed background tasks are permitted, and they cannot run
indefinitely or start on their own. Apple does provide
BGProcessingTask and BGContinuedProcessingTask, but these are not
daemons. They must be triggered by foreground activity, they run only
when the system decides resources are available, and they cannot run
persistently or autonomously like cron, Tasker, or launchd services.
B. iOS does not expose raw sockets, packet capture APIs, or monitor mode,
which prevents full VPN implementations, packet sniffers, Tor relays,
and similar tools.
C. iOS enforces strict sandboxing. Apps cannot access the filesystem
outside their container, cannot inspect other processes, and cannot
hook system events. This prevents full file managers, system-wide
automation tools, and system profilers.
D. iOS forbids JIT and dynamic code execution, which prevents many
emulators and virtual machines.
E. iOS does not allow replacing system components such as the launcher,
dialer, or SMS subsystem.
These are not value judgments. This is just how iOS works.
Apple designed iOS to not be able to run apps that all other OS's run.
Nobody doubts that.
What we're doing here, is simply discussing what those functionalities are.
Specifically, this thread is discussing the technical boundaries which
Apple has chosen for the platform that no other OS vendor has chosen.
Hence, if we can't answer this question, then we know nothing about iOS.
My question was about identifying additional categories of functionality
that are technically impossible on iOS due to Apple's architectural
choices.
If you have further technical information about capabilities that iOS
exposes or does not expose, that would be on-topic for the discussion.
If we don't even know what iOS can't do that all other operating systems
easily do, then we know nothing about how Apple designed iOS, and why.
--
My posts aim to explore how iOS actually works beneath the surface,
as we know nothing about iOS if all we know is Apple propaganda.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
