ARarbayi·Jan 12, 2026Submission
LiteRT – Google's Edge ML Framework
2 points · Open discussiongoogle-ai-edge
LiteRT
C++2025–2026
google-ai-edge / LiteRT
LiteRT
LiteRT, successor to TensorFlow Lite. is Google's On-device framework for high-performance ML & GenAI deployment on edge platforms, via efficient conversion, runtime, and optimization
2Distinct people
2Mentions
0Explicit recommenders
3.6KGitHub stars
What to know before exploring
What it is
LiteRT, successor to TensorFlow Lite. is Google's On-device framework for high-performance ML & GenAI deployment on edge platforms, via efficient conversion, runtime, and optimization
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by day2 dated mentions
Observed mentions: 2025-12-23 18:12:05 UTC to 2026-01-12 12:04:16 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Dec 23 | 2025-12-23 00:00:00 UTC | 2025-12-24 00:00:00 UTC | 1 | 0 | 1 |
| Dec 24 | 2025-12-24 00:00:00 UTC | 2025-12-25 00:00:00 UTC | 0 | 0 | 0 |
| Dec 25 | 2025-12-25 00:00:00 UTC | 2025-12-26 00:00:00 UTC | 0 | 0 | 0 |
| Dec 26 | 2025-12-26 00:00:00 UTC | 2025-12-27 00:00:00 UTC | 0 | 0 | 0 |
| Dec 27 | 2025-12-27 00:00:00 UTC | 2025-12-28 00:00:00 UTC | 0 | 0 | 0 |
| Dec 28 | 2025-12-28 00:00:00 UTC | 2025-12-29 00:00:00 UTC | 0 | 0 | 0 |
| Dec 29 | 2025-12-29 00:00:00 UTC | 2025-12-30 00:00:00 UTC | 0 | 0 | 0 |
| Dec 30 | 2025-12-30 00:00:00 UTC | 2025-12-31 00:00:00 UTC | 0 | 0 | 0 |
| Dec 31 | 2025-12-31 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 1 | 2026-01-01 00:00:00 UTC | 2026-01-02 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2 | 2026-01-02 00:00:00 UTC | 2026-01-03 00:00:00 UTC | 0 | 0 | 0 |
| Jan 3 | 2026-01-03 00:00:00 UTC | 2026-01-04 00:00:00 UTC | 0 | 0 | 0 |
| Jan 4 | 2026-01-04 00:00:00 UTC | 2026-01-05 00:00:00 UTC | 0 | 0 | 0 |
| Jan 5 | 2026-01-05 00:00:00 UTC | 2026-01-06 00:00:00 UTC | 0 | 0 | 0 |
| Jan 6 | 2026-01-06 00:00:00 UTC | 2026-01-07 00:00:00 UTC | 0 | 0 | 0 |
| Jan 7 | 2026-01-07 00:00:00 UTC | 2026-01-08 00:00:00 UTC | 0 | 0 | 0 |
| Jan 8 | 2026-01-08 00:00:00 UTC | 2026-01-09 00:00:00 UTC | 0 | 0 | 0 |
| Jan 9 | 2026-01-09 00:00:00 UTC | 2026-01-10 00:00:00 UTC | 0 | 0 | 0 |
| Jan 10 | 2026-01-10 00:00:00 UTC | 2026-01-11 00:00:00 UTC | 0 | 0 | 0 |
| Jan 11 | 2026-01-11 00:00:00 UTC | 2026-01-12 00:00:00 UTC | 0 | 0 | 0 |
| Jan 12 | 2026-01-12 00:00:00 UTC | 2026-01-13 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesI get the impression that https://github.com/pytorch/executorch is Meta’s take on TFLite / LiteRT, which is quite interesting.
While reading the README and related documentation, I noticed that Samsung Exynos NPU acceleration was listed, which immediately caught my attention. According to
https://docs.pytorch.org/executorch/main/backends/samsung/sa..., Samsung has finally built and released an NPU SDK—so I followed the link to check it out.
Unfortunately, the experience was disappointing.
The so-called “version 1.0” SDK is available only for Ubuntu 22.04 / 20.04. There is no release date information per version, nor any visible roadmap. Even worse, downloading the SDK requires logging in. The product description page itself https://soc-developer.semiconductor.samsung.com/global/devel... does contain explanations, but they are provided alm
Read the rest
ost entirely as images rather than text—presented in a style more reminiscent of corporate PR material than developer-facing technical documentation.
This is, regrettably, very typical of Samsung’s software support: opaque documentation, gated access, and little consideration for external developers. At this point, it is hard not to conclude that Exynos remains a poor choice, regardless of its theoretical hardware capabilities.
For comparison, Qualcomm and MediaTek actively collaborate with existing ecosystems, and their SDKs are generally available without artificial barriers. As a concrete example, see how LiteRT distributes its artifacts and references in this commit:
https://github.com/google-ai-edge/LiteRT/commit/eaf7d635e1bc...