Mob 0.9.17, 0.9.16 and 0.9.15 has been released.
Added
- Async work in screens, the LiveView way.
Mob.Socket.start_async/3runs
a function in a task linked to the screen and delivers{:ok, result}or
{:exit, reason}to the new optionalhandle_async/3callback, so a screen
can render a loading state (a spinner, or skeleton boxes) and fill it in
when the data arrives. A crashing task does not crash the screen, and none of
the task’s messages (:DOWN, the link’s:EXIT) reachhandle_info/2.
Starting a name that is still running replaces the older task and only the
newest reports.Mob.Socket.cancel_async/3always stops the task; its
reason is only whathandle_async/3receives as{:exit, reason}. A
screen’s tasks stop when the screen does, including a
stop with reason:normal.Mob.ScreenCase.render_async/2awaits them in
off-device tests. Mirrors LiveView’sstart_async/3,handle_async/3,
cancel_async/3andrender_async/2. Seedecisions/2026-10-09-screen-async-tasks.md. - Docs for AI agents, in the package and on hexdocs. The Hex package now
shipsguides/and a newusage-rules.md, so an app has
deps/mob/guides/*.mdanddeps/mob/usage-rules.mdmatching its exact mob
version (mix usage_rules.syncpicks the rules file up).usage-rules.mdis
the short version: screens, async loading, lists, navigation, testing, and
where the docs are. It is also on hexdocs as “Usage Rules for AI Agents”.
A new guide, Coming from Phoenix LiveView,
mapsassign_async,start_async, streams,phx-click, navigation and
LiveViewTestto Mob. Guide titles name what they cover (llms.txtlists
titles only), e.g. “Screen Lifecycle & Async Loading”. The README has a “For
AI agents” section, andguides/agentic_coding.mdsays where an app’s agent
finds the docs.
Fixed
- Docs: async loading and pagination examples. The pull-to-refresh and
infinite-scroll patterns inguides/events.mdstarted aTask.async/1and
never handled its reply, so:loading/:refreshingnever cleared; they now
usestart_async/3. The infinite-scroll example usedon_end_reachedon a
<Scroll>and matched{:end_reached, tag}.on_end_reachedis a
<LazyList>prop, and it delivers{:tap, tag}.guides/screen_lifecycle.md
documentshandle_async/3and that slow work inmount/3delays the screen’s
first frame. - Docs: broken and wrong links. The
Mobmodule doc linked
guides/getting_started.htmlandguides/architecture.html, which 404 on
hexdocs.guides/agentic_coding.mdlinked the repos’AGENTS.mdon a
mainbranch that doesn’t exist (it’smaster).
Link: Release 0.9.17 · GenericJam/mob · GitHub
Added
MOB_NODE_HOST: the host a physical iPhone’s node is named after
(MOB-428). A device build names its node<app>_ios@<WiFi IP>whenever
the phone has WiFi; when that WiFi is a network the Mac can’t route to,
the only path is the USB cable (the link-local169.254.x.xaddress), and
the node, though its EPMD answers over the cable, could never be dialled.
mob_beam.mnow takesMOB_NODE_HOSTwhen it is one of the phone’s own
IPv4 addresses (anything else is ignored) and otherwise keeps WiFi →
link-local → loopback. mob_dev 0.7.18’smix mob.connectpasses the
address it reaches the phone at. The choice lives in
ios/mob_node_host.h, covered bytest/native/node_host_test.c. See
decisions/2026-10-09-ios-node-host-override.md.
Link: Release 0.9.16 · GenericJam/mob · GitHub
Added
- Plugin self-test contract (MOB-411).
Mob.Plugin.SelfTestis a
behaviour with one callback,run(%{platform:, device:}) :: :pass | {:fail, reason} | {:skip, :needs_hardware | :needs_user | reason}. A
plugin names its implementation in the manifest asselftest: Module;
mix mob.selftest(mob_dev 0.7.17) and mob_ci call it on the device
over distribution for every activated plugin. A pass means the test got
a real answer back from the plugin’s native code, not that a module
loaded.Mob.Plugin.SelfTest.result?/1says whether a term is a valid
result. SeeMOB_PLUGINS.md(“Self-test”) and
decisions/2026-10-08-plugin-self-test-contract.md.
Link: Release 0.9.15 · GenericJam/mob · GitHub
Mob Info
Classification: Hybrid Mobile Framework
Description: BEAM-on-device mobile framework for Elixir. OTP runs inside your iOS and Android apps — embedded directly in the app bundle, no server required. Screens are GenServers; the UI is rendered by Compose and SwiftUI via a thin NIF.
Forum/tag: mob
Click here to view its main thread on the forum.


















