Pavel Zhovner answers all Your Flipper One Questions!

Tech/Product Overview (Flipper Devices, Flipper One vs. Flipper Zero)

Flipper Devices positioning

Flipper Devices is primarily a hardware company, providing only the necessary software to use the hardware effectively. The company handles full internal engineering—covering industrial design, PCB/mechanics/software, and even marketing creative production (e.g., videos/photos/animations).

Design philosophy

• Flipper Zero emerged from the founder’s frustration with existing tools (e.g., Proxmark, HydraNFC, Arduino/Raspberry Pi projects) that were powerful but not pocketable/easy to use.
• Flipper One represents a shift away from the “Swiss Army knife radio” concept toward a more compact computing platform—compared to a small PC (especially because it separates layers, such as a Linux/CPU side vs an MCU side).

---

Why Flipper One (and not Flipper Zero “Mark II”)

• Even if it would capture attention sooner, the founder says it’s more important to build what the team truly cares about.
• The team iterated/redesigned the Flipper One concept over years, rather than releasing a “v2” earlier.
• The core motivation includes addressing perceived shortcomings of single-board computers—e.g., the discomfort with small HDMI form factors and a preference for full-size HDMI and better convenience.

---

Software/OS Decisions (Flipper OS; Linux Compatibility vs. “Mainstream Desktop OS”)

Avoiding “Nyx OS” as a base

• The goal isn’t to expose complex user-space tooling intended for general “civilian” users.
• They want Ubuntu/Debian-style how-to guides to work on Flipper One.

Openness and extensibility

• Flipper OS is intended to remain open enough that alternative firmware/distros could exist across the Flipper Zero/One ecosystems (implied via community).
• A likely early alt implementation mentioned/predicted: Kali Linux.

---

Hardware Architecture Questions (MCU vs. CPU Utility)

• MCU standalone use: Unlikely to be fully standalone like Flipper Zero.
• Independent MCU applications: The MCU can still support local apps:
  • MCU GPIO pins are broken out (rear GPIO connected to the MCU), enabling some independent functionality without Linux.

---

Battery Life Expectations (Scenario-Dependent)

Battery life is highly dependent on use case, especially:

• Whether graphics/display subsystems (e.g., HDMI/display) are active vs headless operation.
• Software tuning can roughly double battery life (claim).

A target scenario is enough runtime for media-box-like viewing (e.g., watching a full movie or two).

---

Use Cases Highlighted by the Founder (“What It’s For”)

Primary themes:

• Travel connectivity
• Emergency/always-on links
• Local AI/config generation
• RF/SDR experimentation

Travel connectivity: hotel internet troubleshooting

• Diagnose wired vs Wi‑Fi issues when hotel internet is unreliable.

Improving cell connectivity

• Use directional/external antennas to locate towers and improve connectivity, particularly when 5G is weak.

Emergency access / always-on connectivity

• eSIM concept: an annually paid, low-cost plan for slow but continuous connectivity.
• If home internet/electricity goes down, Flipper One should send mobile notifications via cellular.

SDR + wideband listening experiments

With sufficient CPU performance:

• Connect SDR / walkie-talkie modules
• Listen across very wide frequency ranges (conceptually spanning aircraft and satellite communications)

Offline AI assistance

• Local AI (small language model) to generate VPN/Wi‑Fi configs offline.
• Example: generate a VPN config while traveling when banking/accounting apps fail in another country—without relying on external services.

---

Extensibility & Modules (Company vs. Community)

Key enabling hardware: M.2 port connector

The M.2 port connector is positioned as a major enabler to “turn it into pretty much anything.”

Company-built modules (planned, but not immediate)

• They want to build modules but lack time right now.
• They’ve already produced mock-ups/demos using Arduino-like approaches and existing radio boards.
• Example interest: a walkie-talkie module.

Third-party/community module vendors

• The plan includes supporting third-party module vendors, including SDR-related makers.

---

Integration With Flipper Zero (Possible Connection Paths)

They are not planning a “Flipper Two”-style merged device by default (i.e., automatically combining Flipper Zero radios into Flipper One).

Technical possibilities mentioned:

• Flipper One can connect to Flipper Zero via USB (USB host is present).
• Another concept: run Flipper Zero software inside Linux on Flipper One.

Strategic stance:

• Prefer designing from real applications/usage rather than building a feature first for its own sake.

---

Next Roadmap: Connectivity Layers + Satellite

• No clear plan for a “Flipper Two/10.”

Planned major additions:

• Integrated eSIM (referenced as “EC”) via operator partnerships so the device can ship cellular-internet ready.
• Satellite communication:
  • They intend to run their own Cube Satellite (described as potentially not very expensive).
  • They’re exploring NTN (non-terrestrial network) options, including discussion with Skylo.

Vision:

• A global “rescue/survival gateway” for IoT and travel.

---

Security/Defense Positioning (Home Security Hub Concept)

Not framed as “pentest/offense defense,” but defensive monitoring:

• A home sensor/honeypot that connects to the home network to detect scanning/exploitation attempts and notify the user.

Example in a hosted setting (Airbnb-like):

• Use a USB webcam as a covert “motion detector” and send alerts; it shouldn’t look like obvious CCTV.

Also described as:

• An IoT hub + emergency internet access when normal connectivity fails.

---

Kickstarter and Pricing Expectations (Business Constraints)

Timing

• Hoped to start within several weeks (also phrased as “several months”).

Pricing target

• Ideal target: $300–$350.
• Constraints:
  • Large pre-orders needed due to chip availability and a RAM crisis.
  • Otherwise cost could rise toward $1,000, which they aim to avoid.

Kickstarter purpose

Includes both:

• Product work, such as UI/power behavior details (e.g., reboot press duration, screen/pixel feel/look)
• Communications/materials, with campaign videos identified as a major difficulty/risk

---

Main Speakers / Sources

• Pavel Zhovner — Founder and CEO of Flipper Devices (speaker/primary source)
• David — Interviewer (name given as “David” in subtitles)