Complete STIQRA manual

Why STIQRA is different

STIQRA helps you follow articles from the websites and publishers you choose. Many websites offer a list of their latest articles, called a feed (sometimes labelled RSS or Atom). STIQRA brings these updates into one place so you can spend less time checking individual sites.

The app helps you read, organise, and search articles without ads or a reading profile built for advertising. It keeps most of your reading activity on your device, and makes it clear when you choose to send content to another app or service.

Local-first reading and organisation

Reading state, saved items, archive state, history, filters, topic choices, metrics, cached images, reports, audio metadata, and related preferences are designed to stay on your device unless you choose an external action such as export, share, open, copy, import, or handoff to another app.

STIQRA does not need a remote analytics service to organise your reading library. Local-first does not mean the app never uses the network. It means network use is tied to the reading work you asked it to do: fetching articles from your chosen RSS/Atom sources, loading article images when image loading is enabled, or opening an external destination you choose.

More ways to work with articles

You can follow many websites in one place, focus on a topic, compare articles about the same story, and save what you want to read later. Your original sources stay visible, so you can always check where an article came from.

Track topics, Search, related stories, and Feed Stats help you find and organise articles. If you want to go further, translation, reports, and audio briefings are optional where available. You decide when to use them.

Direct access to user-approved feeds

STIQRA is not a central news service. The app connects directly to enabled RSS/Atom feeds under exact public HTTPS origins you reviewed and approved for each subscription, with XMAKYNA out of the normal content path. You can start with a public website address: STIQRA looks for a supported feed advertised by that site. A normal webpage cannot become a feed unless the site offers one. You can also add a public feed address directly.

That matters for resilience. If XMAKYNA operated as the required fetch service for every source, an XMAKYNA outage could make the whole reading system unusable. STIQRA's model keeps article collection closer to the distributed nature of RSS and the web: each publisher remains its own source.

Several sites can depend on the same internet service, so a problem there may affect more than one source. For example, publishers may share hosting companies, content-delivery networks (CDNs), website address services (DNS), or bot-defence tools. Feed Stats helps show when sources are delayed or unavailable.

Built to help you finish, not keep you scrolling

STIQRA is designed to help you understand your sources faster. It is not an ad-supported feed designed to maximise scrolling time.

XMAKYNA does not serve ads, so STIQRA does not need to optimise for impressions, eyeball time, or compulsive engagement. The app should help you do the reading job and leave; it should not try to keep you inside the app for XMAKYNA's benefit.

That is why STIQRA includes features such as filtering, source health, saved views, summaries, related-story clusters, Top Keywords drill-downs, batch actions, article previews, report workflows, audio briefings, read-state controls, and time-saved metrics. These are meant to reduce wasted time, not capture more of it. Unread and source badges are task-state indicators, not streaks or pressure loops. Auto refresh is Off by default for new installs so periodic feed checks begin only after you enable them.

Fewer hidden surfaces

STIQRA is designed to do the reading job directly. It does not require an XMAKYNA fetch service in the normal reading path.

Adding services to the reading process can introduce extra failures, data sharing, or background activity. STIQRA aims to avoid services that are not needed for reading.

Following websites, loading article images, opening links, sharing, and exporting data can still contact websites or other apps. Those actions are tied to what you choose to do. Auto refresh is Off by default for new installs; you decide whether to turn it on.

STIQRA still connects to enabled feeds under their exact user-approved capabilities and, when images are enabled, to public image hosts referenced by those articles. Those are external sources and are treated carefully. But the app should not add unrelated third-party traffic just to make the product easier to monetise or monitor.

STIQRA's shipping code is built from XMAKYNA-owned Swift code and Apple platform frameworks. It has no third-party code packages, advertising SDKs, analytics SDKs, or tracking SDKs. XMAKYNA does not add tracker, advertising, or analytics calls to the normal reading workflow.

That shipping-code claim is different from runtime network and service use. User-approved feed, article, and image origins are network destinations, not compiled software dependencies. When iCloud Sync is enabled, STIQRA uses Apple's CloudKit/iCloud infrastructure, which is an Apple-operated platform service rather than XMAKYNA-operated infrastructure. The optional ChatGPT handoff is an explicit user action and does not embed an OpenAI SDK or OpenAI API package.

What STIQRA refuses to add

A useful reader should not become a small advertising platform, analytics collector, or remote-control surface just because that is common in software. STIQRA is intentionally designed without several categories of hidden machinery:

SurfaceWhy STIQRA avoids it
Advertising SDKsAds create impression incentives, third-party content surfaces, and network behaviour unrelated to reading.
Tracker and attribution SDKsThey expand the user’s data surface and can make idle/background activity harder to explain.
A required XMAKYNA feed proxyA central proxy would make XMAKYNA a bottleneck for normal reading and a single failure domain.
Diagnostic-only feed probesSource diagnostics should come from normal refresh work, not hidden extra traffic.
Engagement loopsSTIQRA should help you finish the reading task, not train you to keep scrolling.

This is part of the product design, not just a privacy setting. The app should give you useful reading tools without quietly adding unrelated systems that you did not ask for.

External content is not trusted by default

STIQRA is strict about RSS/Atom source URLs, imported files, generated reports, clipboard content, app handoffs, and article images because external content is not trusted by default. This strictness is part of the product: it helps keep the app useful, predictable, and easier to reason about.

STIQRA checks information received from websites, imported files, and other apps before using it. It can reject unsupported or unusually large content, and it avoids opening untrusted content as active webpages inside the reader. These safeguards reduce risk but do not guarantee that a publisher's information is correct.

Article images come from external websites and are treated as untrusted input. STIQRA can reject, quarantine, normalise, or avoid images that are malformed, unsupported, oversized, repeatedly failing, or unsafe to display. You can turn image loading off at any time.

User-visible engineering rules

STIQRA's behaviour is shaped by the same engineering rules used to build it: visible counts should match what you are looking at, offline state should remain usable, external content should be treated defensively, and external handoffs should be visible before your work leaves the app.

In day-to-day use, that means:

  • Counts and batch actions should follow the current visible scope.
  • Feed data should remain useful from local state when the network is unavailable.
  • Feed, image, import, generated-text, clipboard, and handoff paths should treat incoming content carefully.
  • Opening a browser, sharing, copying, exporting, importing, or handing work to another app is a product boundary.
  • Feed Stats should explain normal refresh behaviour without creating hidden diagnostic probes.
  • Related-story clusters should make repeated coverage easier to compare without hiding the underlying articles.
  • Audio briefings and report workflows should preserve reviewable source inputs and stay optional.

Why STIQRA starts on Apple platforms

STIQRA starts on macOS and iOS because Apple platforms give us strong native tools for the way we build: Swift, SwiftUI, sandboxing, and system privacy controls. Local state remains authoritative and persists on each device. When iCloud Sync is available in your build, optional cross-device synchronisation is off until you enable it in Settings → Security & Privacy → iCloud Sync; see iCloud Sync for the exact synced and device-only boundaries.

That does not make XMAKYNA Apple-only. It means STIQRA begins where we can deliver the strongest native version of this product today.

The practical result

The result should feel quieter than a typical feed or news product. When STIQRA is not refreshing, opening a source, loading an image you allowed, exporting, sharing, or handing content to another app, it should not have a hidden reason to keep working in the background.

That quietness is not a decorative claim. It is what follows from the business and engineering choices above: no ad loop to feed, no tracker SDK to satisfy, no required XMAKYNA content broker, and fewer unnecessary components to wake up, call home, or fail.

For practical setup, return to Getting started. For detailed data boundaries, continue to Privacy, security, and data. For source diagnostics, see Metrics and Feed Stats.