Netafim

Netafim partnered with moblers to bring GrowSphere™ irrigation and fertigation workflows to a Flutter application for iOS and Android. The 12-month engagement covered product specification, UX/UI and cross-platform development for field maps, schedules, sensor information, logs and alerts. Source: moblers’ retained Netafim project record.

Confirmed moblers delivery

• Detailed product specification and UX/UI design.
• Flutter application for iOS and Android.
• Interactive map for selecting fields and irrigation zones.
• Irrigation and fertigation scheduling, logs and alerts.
• Sensor-driven monitoring views.
• Modular client experience for multiple Netafim systems and sensor workflows.
• Team: Project Manager, Product Owner, QA, 2–3 developers, led by moblers’ CTO. Source: moblers’ retained Netafim project record.
• Delivery duration: 12 months. Source: moblers’ retained Netafim project record.

Exact project start and end dates, milestone dates, team member names, final developer headcount, and post-delivery responsibility are not publicly documented.

Screens and workflows delivered in the 12-month engagement

The public project record attributes these client capabilities to the moblers delivery:

• Field map and field/zone selection: an interactive map for navigating fields and choosing irrigation zones.
• Zone-level irrigation controls: mobile controls for viewing and operating irrigation zones.
• Irrigation and fertigation schedule editor: workflows for creating and reviewing watering and fertilization schedules.
• Logs and alerts: client views for operational history and system notifications.
• Sensor dashboards: monitoring screens that present sensor readings and state.
• Modular multi-system experience: client architecture intended to support multiple Netafim systems and sensor workflows.
• Cross-platform product UX: specification, UX/UI and Flutter implementation for iOS and Android.

These are high-level delivered workflows. Public records do not map them to design-handoff, beta or production dates; identify the release in which each first appeared; or disclose whether later Netafim releases changed them.

Current availability

GrowSphere is currently public on both mobile stores:

• GrowSphere on Apple App Store — published by NETAFIM LTD for iPhone and iPod touch; requires iOS 12.0 or later.
• GrowSphere on Google Play — published by NETAFIM LTD; Google Play currently shows 1K+ downloads.

Store metadata reflects the current Netafim product, not necessarily the versions delivered during the historical moblers engagement. At verification on 3 September 2026, the Google Play listing showed an update date of 20 May 2026; the Apple App Store listing showed version 2.8.7. Market, controller, sensor and account availability may vary.

How to interpret current store metadata

The store listings establish current availability, publisher of record, current compatibility statements and a public Google Play download band. They do not identify which release corresponds to the historical moblers-delivered build, who implemented a later feature, or whether current screenshots reproduce the original design.

Mapping version 2.8.7, the 20 May 2026 Google Play release or any later store version to the 12-month engagement requires Netafim’s release notes, source-control history or contractual delivery records. None is available in the public project archive.

Feature-to-release mapping

The public evidence supports the following concise mapping. “Not publicly documented” means the delivered workflow is named in moblers’ retained project record, but no approved source ties its first appearance to a store version or date.

Delivered workflow	First-known release version	First-known release date	Evidence boundary
Field map and field/zone selection	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Zone-level irrigation controls	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Irrigation and fertigation schedule editor	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Logs and alerts	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Sensor dashboards and monitoring views	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Modular multi-system experience	Not publicly documented	Not publicly documented	Delivered workflow is recorded; release mapping is absent
Cross-platform Flutter UX for iOS and Android	Not publicly documented	Not publicly documented	Flutter and both platforms are confirmed; version mapping is absent

To replace any “not publicly documented” value, a source must connect the workflow to a release: Netafim release notes or release log, source-control tag/commit history, or a contractual milestone or handoff record. Current Apple version metadata and the Google Play update date do not provide that historical mapping.

Pricing, licensing and commercial terms

The public project record does not contain GrowSphere pricing, licensing or commercial terms, so this page does not compare its cost with alternatives. No authorized source currently states:

• Pricing tiers or currency, including per-device, per-farm, per-user or enterprise rates.
• Subscription, perpetual, OEM or freemium licensing, or feature gates.
• Ongoing support or maintenance fees and billing cadence.
• Trial, demo, discount or reseller terms.
• Typical contract length or renewal terms.

Publishing a commercial comparison requires a dated Netafim price sheet, licensing document, proposal template or other authorized source covering the same market and scope. Without one, a price comparison would be speculation.

Technical stack and architecture

Confirmed implementation

Flutter is the only named framework confirmed for the moblers mobile implementation. The client was built for iOS and Android and presents maps, schedules, logs, alerts, telemetry and irrigation controls.

Why implementation detail is withheld

The absence of version numbers and library names on this page is a disclosure decision, not missing knowledge. GrowSphere is Netafim’s product, and moblers treats client codebase details as confidential: framework and SDK versions, dependency inventories, mapping providers, state-management and storage choices, native module structure, test and CI/CD tooling, release-signing workflow, backend runtime, cloud provider, API and authentication design, broker and protocol selection, telemetry intervals, and encryption or key-management specifics are not published without written client approval.

The same applies to an architecture diagram of the engagement: no approval exists to publish one, so this page shows only the architecture Netafim itself documents publicly. Prospective clients evaluating moblers’ capability should request a technical reference conversation under NDA rather than expecting this level of detail on a public page.

The following engagement-specific details are therefore not published:

• Flutter and Dart versions.
• Minimum Android API and the historical iOS deployment target.
• Native iOS/Android modules and languages.
• State management, local storage, mapping SDK and geospatial libraries.
• Automated-test frameworks, CI/CD, release signing and monitoring.
• Backend language/framework, databases, hosting or cloud provider.
• API style, authentication, authorization and device identity.
• Sensor protocols, brokers, queues and real-time transport.

Public GrowSphere architecture

Netafim’s GrowSphere digital-farming overview describes the current product path as:

Controllers + field sensors → cloud services → GrowSphere mobile/web experience

Netafim says the system integrates hydraulic, operational and agronomic information, supports real-time field monitoring, and provides remote and offline control for limited-connectivity areas. These are product-level capabilities; the public material does not identify MQTT, HTTP, WebSockets, LoRaWAN, Modbus, REST, GraphQL or any other production protocol.

Not publicly disclosed: architecture style, cloud provider, service boundaries, endpoint names, brokers, databases, telemetry intervals, average or p99 latency, buffering location, caching, conflict resolution, retry/backoff behavior, encryption, retention, scaling model and SLA.

Sensors, controllers and data flow

Netafim’s GrowSphere Monitoring documentation publicly groups integrated sensors into:

• Soil sensors: soil moisture and related measurements at different depths.
• Plant sensors: trunk radius, small-plant diameter and remote NDVI.
• Hydraulic sensors: water meter, pressure sensor and pressure switch.
• Weather sensors: solar radiation, relative humidity and precipitation.

The GrowSphere ONE installation guide describes ONE as a stand-alone cellular monitoring unit using 3G/4G coverage and a global SIM. It names sensor examples including NetaCap WET150, NetaSense Tensiometer, SM150T, pressure, temperature/humidity and dendrometer devices. The setup flow creates or selects a farm, assigns the device, chooses and names sensors, shows wiring instructions, and validates readings.

Current store release notes also reference GrowSphere MAX and FLEX controllers. Public sources therefore establish controller/sensor → cellular/cloud → app behavior at a high level.

They do not establish which of these current devices were part of the original moblers scope, nor the gateways, firmware, protocol, vendor SDK, backend API, command path, telemetry interval, edge buffer or resilience controls used during that engagement.

Historical hardware scope versus later product evolution

The original project record confirms integration with multiple sensor types and Netafim systems, including a dedicated app for a specific sensor product. It does not name a sensor model, controller model, gateway, SIM, firmware version or vendor SDK.

Accordingly:

• GrowSphere ONE, MAX and FLEX are confirmed current product references, not confirmed original-scope controllers.
• NetaCap WET150, NetaSense Tensiometer, SM150T, pressure, temperature/humidity and dendrometer devices are confirmed current documentation examples, not confirmed original-scope sensors.
• No public release or contract record ties any named model to the moblers engagement.

This distinction prevents later GrowSphere product evolution from being retroactively attributed to the original delivery.

Offline, security and operational behavior

Netafim publicly advertises offline and remote control for areas with limited connectivity, but does not publish the mobile caching model, queued command behavior, synchronization rules, conflict resolution, replay window, retry policy or failure modes.

The current Google Play data-safety declaration states that the developer reports no data shared with third parties and no data collected. The Apple App Store privacy disclosure separately identifies possible handling of location, user content, identifiers, usage data and diagnostics linked to identity. Store disclosures can differ by platform, feature and region; they are current publisher declarations, not a technical security audit.

Authentication method, device credentials, TLS versions, encryption at rest, key management, data residency, retention, RBAC, audit logs, penetration testing and compliance controls used in the moblers engagement are not public.

Results and measurable impact

Confirmed public figures:

• Delivery: moblers completed the application engagement in 12 months. Source: moblers’ retained Netafim project record.
• Current adoption floor: Google Play displays 1K+ downloads as of 3 September 2026.

The store count is current public distribution evidence, not a measured project result or total cross-platform user count.

Netafim’s product materials describe reduced field effort, more reliable planning and execution, remote monitoring, alerts, and the combination of hydraulic, operational and agronomic information. Its article Simplifying Farming: The Role of GrowSphere contrasts remote app management with a two-hour drive to inspect a distant field; this is an illustrative workflow, not a measured before/after average.

Not publicly disclosed for the moblers engagement:

• Total or monthly active users and combined iOS/Android installs.
• Baseline and post-launch irrigation efficiency.
• Water use per hectare or cycle and attributable reduction.
• Grower time saved per task, day or week.
• Crop yield or quality improvement.
• Reliability, alert reduction, latency or uptime.
• Cost savings, revenue impact or ROI.
• Measurement window, cohort and methodology for any of the above.

No generic Netafim water-saving statistic should be presented as an outcome of this app project without a matched cohort, baseline and approved attribution.

Why no project KPIs appear here

Two distinct reasons apply, and they should not be conflated.

First, agronomic outcomes such as water saved, irrigation efficiency and yield are properties of the customer’s farm operation, sensors and agronomy — not of a mobile client. Attributing them to app development would require a controlled cohort with a baseline, a defined measurement window and Netafim’s own field data. No such study is attributed to this engagement.

Second, product telemetry that could support adoption metrics — active users, retention, session behavior, crash and latency data — belongs to Netafim, not moblers. moblers does not publish a client’s product analytics.

The practical consequence: the only figures on this page are the 12-month delivery duration and the public Google Play download band. Any additional metric would need a named source document, an approver, a cohort, a measurement window and a method, supplied by Netafim.

Client evidence

Netafim’s own GrowSphere materials provide current product evidence. The Netafim article Simplifying Farming: The Role of GrowSphere quotes agronomist Cuong Doan explaining that farmers appreciate receiving daily recommendations directly in the mobile app and can apply minor adjustments based on crop variety and weather.

This quote supports the usefulness of the current GrowSphere workflow; it is not a testimonial about moblers, does not provide a numeric project KPI, and should not be represented as client approval of this case study. No named Netafim executive quote evaluating moblers or permission record for a testimonial is publicly available.

Support, maintenance and handover

Public project material confirms the 12-month delivery but does not define:

• Post-delivery support or maintenance dates.
• Support contacts, hours or escalation path.
• Severity levels, response and resolution targets.
• Bug-fix, security-patch or feature-release cadence.
• Monitoring, hosting or operational responsibility.
• Handover documents, runbooks or training titles and delivery dates.
• Whether support was included, ongoing or separately priced.

Current releases on Google Play and the Apple App Store show that Netafim continues to update the product, but they do not establish that moblers performs that work. Contractual support terms should be confirmed from the applicable Netafim–moblers agreement.

For a definitive support or handover answer, readers need the applicable agreement or written confirmation from Netafim identifying the support owner, coverage dates, contacts, escalation path, severity definitions, SLA targets, release ownership, hosting/monitoring ownership, and any runbooks or training delivered. None of those contract records is reproduced on this public page.

What store records do establish

One ownership question is answerable from public records rather than the contract: Netafim is the publisher of record. Both listings are published by NETAFIM LTD, and Apple’s listing names NETAFIM LTD as seller with a Netafim copyright. Releases therefore ship under Netafim’s developer accounts, and Netafim controls store presence, versioning and distribution.

Store records do not, however, identify who writes the code behind each release, who operates the backend, or who holds a support obligation. Those remain contractual matters. moblers also does not publish its own support SLAs for client-owned products on project pages, because scope and response targets are negotiated per engagement rather than offered as a standard public tier.

Responsibilities

Confirmed moblers responsibility: specification, UX/UI, Flutter cross-platform development, map and scheduling workflows, sensor-driven client views and multi-system compatibility.

Not publicly allocated between Netafim and moblers: hardware, firmware, controller and sensor documentation, cloud/backend ownership, APIs, live field streams, test farms, product requirements and production operations. App-store publishing is the exception — public store records show Netafim as publisher of record.

Individual team members are described by role rather than by name. moblers publishes role composition (Project Manager, Product Owner, QA, 2–3 developers, CTO-led) but does not publish employee names, titles or headcount attribution on client project pages without each person’s consent and client agreement. Requests for a named delivery reference can be handled directly.

Visual evidence

The available project archive contains one retained asset:

• public/images/projects/netafim/cover.jpg — JPEG, 722×527 pixels. Caption: Aerial agricultural field with a conceptual connected-farming overlay linking machinery, satellite, agronomy, tractor and mobile symbols. Source: retained asset metadata inspected in the moblers project archive.

This is cover artwork, not a screenshot of GrowSphere. Its capture or creation date, creator, original high-resolution file, design source, publication-license record and required attribution are not present in the available materials. Its inclusion in the existing site archive confirms current site use, but does not independently establish broader reuse rights.

Current GrowSphere screenshots are available on the linked Apple and Google store listings. They are current Netafim publisher assets and are not copied or relabeled here as historical moblers-delivered screens. No release mapping connects those screenshots to the 12-month engagement, and no separately approved map, schedule, log, alert or telemetry screenshot is retained locally.

Prospective technical references

moblers evaluates technical-reference conversations case-by-case. A requester should provide:

1. Company name and project context.
2. The specific implementation or delivery topics they want to validate.
3. An NDA point of contact and relevant availability.

moblers then determines whether Netafim permission is required, whether a mutual NDA must be signed, which engagement-specific materials can be discussed, and an available meeting window. No standard scheduling lead time, automatic eligibility or guaranteed document package is published.

Public request checklist for an NDA conversation

Subject to Netafim permission and a mutual NDA, a technical-reference conversation may cover:

• Architecture notes and approved high-level service boundaries.
• Approved framework or SDK versions and dependency categories.
• Mobile architecture, state-management patterns and local-storage approach.
• Testing strategy, automated-test frameworks and CI/CD/release practices.
• Release signing, version history and beta/production mapping.
• Mapping, telemetry and sensor integration patterns.
• Team-delivery experience and role composition.

This checklist identifies topics a requester may ask about; it does not confirm that every topic or artifact will be approved for disclosure. The process never promises source code, credentials, production endpoints, security secrets, personal data, proprietary Netafim telemetry, or materials moblers is not authorized to disclose.

Evidence boundary

Current GrowSphere product documentation	Original moblers-delivered scope
Current Apple and Google store listings, publisher metadata and screenshots	Product specification, UX/UI and Flutter cross-platform development
Current GrowSphere ONE, MAX and FLEX references and named sensor examples	Interactive field maps, field/zone selection and zone controls
Current Netafim claims about remote monitoring, offline control and integrated agronomy	Irrigation/fertigation scheduling, logs, alerts and sensor-driven views
Describes GrowSphere as it exists today and may include later product evolution	Records a 12-month engagement and role composition, without calendar dates or named personnel

In short, Netafim’s current GrowSphere documentation describes the product today; moblers’ retained project record documents the high-level scope delivered during the 12-month engagement. They overlap in capability language, but public records do not establish which current controller or sensor models, store releases, screenshots or later changes were part of the original moblers scope. Named implementation technologies, security controls, additional project KPIs, support obligations and ownership boundaries remain omitted until Netafim or an authorized engineering source confirms them.