Packages

mob

0.6.8
0.7.20 0.7.19 0.7.18 0.7.17 0.7.16 0.7.15 0.7.14 0.7.13 0.7.12 0.7.11 0.7.10 0.7.9 0.7.8 0.7.7 0.7.6 0.7.5 0.7.4 0.7.3 0.7.2 0.7.1 0.7.0 0.6.26 0.6.25 0.6.24 0.6.23 0.6.22 0.6.21 0.6.20 0.6.19 0.6.18 0.6.17 0.6.16 0.6.15 0.6.14 0.6.13 0.6.12 0.6.11 0.6.10 0.6.9 0.6.8 0.6.7 0.6.6 0.6.5 0.6.2 0.6.1 0.6.0 0.5.18 0.5.17 0.5.16 0.5.15 0.5.14 0.5.11 0.5.10 0.5.7 0.5.6 0.5.5 0.5.4 0.5.3 0.5.2 0.5.1 0.5.0 0.4.0 0.3.10 0.3.9 0.3.8 0.3.7 0.3.6 0.3.5 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.2.0 0.1.0

BEAM-on-device mobile framework for Elixir

HexDocs

Current section

Files

Jump to
Readme
75 Versions
1 Dependency
Dependants
Files
Activity
mob CHANGELOG.md
Raw

CHANGELOG.md 

# Changelog



All notable changes to **mob** are documented here.



Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Versioning: [SemVer](https://semver.org/spec/v2.0.0.html).



Full module documentation: [hexdocs.pm/mob](https://hexdocs.pm/mob).



---



## [0.6.8]



### Added

- **`Mob.Camera.start_frame_stream/2` now works on Android.** The

  Camera2 + CameraX `ImageAnalysis` use case is wired through to BEAM

  as `{:camera, :frame, %{bytes, width, height, format, timestamp_ms,

  dropped}}` messages. Previously this NIF returned `:unsupported` on

  Android — iOS-only. The Android implementation supports the same

  `format: :rgb_f32` the iOS side does (`:bgra_u8` planned for a

  follow-up).

- **`Mob.Canvas` moduledoc** documents the viewport-scaling contract:

  the `width`/`height` props are logical viewport units, NOT pixels.

  The renderer scales draw-op coordinates against the actual on-screen

  pixel size. New tests in `test/mob/canvas_test.exs` pin the

  contract so future readers don't regress to interpreting them as

  raw pixels.



### Notes

- Combined with `mob_dev 0.5.9`'s `mix mob.enable tflite` and the

  `nx_tflite_mob 0.0.3` Hex package, the cross-platform live YOLO

  demo (`mob_yolo_demo`) now runs end-to-end with only Hex deps.

  Measured perf: 24 ms iPhone SE A15 via Core ML → ANE; 75–117 ms

  Moto G Power 5G (Dimensity / BXM-8-256) via NNAPI / `mtk-gpu_shim`.



## [0.6.7]



### Added

- `guides/mobile_surface_matrix.md` — comprehensive audit of mob's mobile capability surface vs. React Native + Expo SDK reference. Tables across UI components, gestures/input, device/system, storage, camera/audio, connectivity, sensors, location, notifications, background tasks, auth/payment, ML/Vision, maps, accessibility, iOS-only, Android-only, plus an "architecturally not present" section. Per-row status (✅ / 🟡 / ❌ / ⛔) with iOS + Android indicators. Hand-maintained from inspection of `lib/mob/` and `src/mob_nif.erl`. Sets realistic expectations and surfaces plugin candidates.

- README link + hexdocs entry so the matrix is discoverable for new users.

- `RELEASE.md` "Tests + docs for new functionality" section now includes a `mix docs` preview step and clarifies that hexdocs publishing is automatic via `mix hex.publish` (rides along from the previously-unreleased doc improvement).

- `MOB_PLUGINS.md` — plugin manifest schema spec covering five plugin tiers (pure Elixir helper through embedded sub-app), worked examples per tier, install + activation flow, schema reference, validation rules, hot-push compatibility table, plugin_spec_version forward-compat. References from the matrix's ❌ rows as plugin candidates.



## [0.6.6]



### Added

- `RELEASE.md` — canonical release-process documentation covering the

  mix.exs-driven trigger model, the patch-bump-default-with-mandatory-

  permission rule, CHANGELOG conventions, when a bump is warranted (new

  functionality, bug fixes, doc improvements, dep bumps) vs. when it

  isn't (CI tweaks, hook changes, internal refactors), the

  tests-and-docs-with-new-functionality non-negotiables, and the

  per-step idempotency of `release.yml`. Linked from `mob_dev` and

  `mob_new` CLAUDE.md by URL so the canonical process is one file.

- `.githooks/pre-push` — committed pre-push hook that runs the cheap

  preflight (format + credo + warnings-as-errors) on every push and

  the full release preflight (test suite + `mob.security_scan` where

  present) only when `mix.exs` changed. Activate per-clone with

  `git config core.hooksPath .githooks`.

- `CLAUDE.md` "Release flow" section linking to the new docs.



## [0.6.5]



### Fixed

- HexDocs source links pointed at the non-existent `main` branch — corrected to `master` so each `</>` glyph next to a heading now opens the actual source file in the GitHub repo.

- `mob_nif.zig` called the variadic `enif_make_list/2` (not exposed in `mob_erts.zig`) from the BT paired-list finisher; the Android arm64 build failed at link. Switched to the non-variadic `enif_make_list_from_array(env, &empty, 0)`.



### Added

- `.github/workflows/test.yml` — runs `mix test`, `mix format --check-formatted`, `mix credo --strict`, `mix erlfmt --check src/`, `xcrun clang-format`, `swiftlint`, and `mix deps.audit` on push to master and on every PR.

- `.github/workflows/release.yml` — on tag push, creates a GitHub Release whose body is the matching `## [X.Y.Z]` section from this changelog (falls back to auto-generated commit notes if the tag has no section).

- `PLAN.md` — three-layer CI + integration-test plan covering the gap between unit tests and on-device verification.



## [0.6.4]



### Added

- `Mob.GpuView` / `Mob.UI.gpu_view/1` — Metal fragment-shader surface on iOS. Host owns the vertex shader (full-screen quad with `v_uv`); user supplies an MSL fragment shader plus a list of uniforms packed at natural alignment into fragment-buffer slot 0. SwiftUI `MobGpuView` wraps an `MTKView` with a hash-keyed shader cache and a translucent red overlay for compile errors. iOS-only in this release; the Android GLES 3.0 backend ships in mob_new 0.3.1.

- `<GpuView>` tag whitelisted for both `priv/tags/ios.txt` and `priv/tags/android.txt`.



## [0.6.3]



### Fixed

- iOS camera sensor delivered frames in landscape-right by default — `Mob.Camera.start_frame_stream/2` was feeding 90°-rotated pixels to ML models, dropping classification accuracy enough that a jar appeared as "laptop 24%" instead of "cup 96%". `AVCaptureConnection.videoRotationAngle = 90` (iOS 17+) / `videoOrientation = .portrait` (older) is now set on both the preview layer and the data-output connection, so what the user sees and what the model sees are the same upright frame.



## [0.6.2]



### Added

- `Mob.Camera.start_frame_stream/2` and `stop_frame_stream/1` — push-driven per-frame delivery as `{:camera, :frame, %{bytes, width, height, format, timestamp_ms, dropped}}`. Defaults to 640×640 `rgb_f32` for direct Nx hand-off; caller-overridable width/height/format/facing and a software `throttle_ms` gate.



### Changed

- iOS camera now uses a single shared `AVCaptureSession` for preview and frame stream. The previous two-session design silently dropped frames because iOS allows only one active session per physical camera.



## [0.6.1] and earlier



Earlier releases predate this changelog; consult the [tag list](https://github.com/genericjam/mob/tags) and the per-tag commit messages for history.