Transformative Apps | Apply Online

FAQs: DARPA Transformative Apps (BAA 10-41)

What is the DARPA Transformative Apps opportunity (BAA 10-41)?

DARPA Transformative Apps (BAA 10-41) is a government funding opportunity focused on getting useful mobile software into the hands of warfighters quickly. It emphasizes a development and acquisition approach that looks more like a modern commercial app ecosystem than a traditional defense software program.

What is DARPA trying to achieve with this program?

DARPA describes two connected goals: (1) deliver a broad set of mission-relevant mobile apps, and (2) prove a faster, repeatable model for acquiring, maintaining, and evolving defense software that can transition to the Services and continue beyond the program.

What is the central concept behind the program?

The program centers on creating a military-oriented apps marketplace where developers and end users work closely together. The marketplace is intended to support proposing, building, vetting, delivering, updating, and improving capabilities on rapid cycles.

What are the main technical Areas of Interest (AOIs) in the solicitation?

The solicitation highlights four main AOIs: (1) Apps Marketplace Architecture, (2) Applications Development, (3) Middleware Services and Libraries, and (4) Network Infrastructure.

What does the Apps Marketplace Architecture area cover?

This AOI focuses on the design of the marketplace itself and the collaboration infrastructure around it. It includes architectures, tools, and processes for vetting apps (such as automated code validation, security checks, and quality assurance workflows), as well as community features that encourage idea sharing and innovation between users and developers.

Does the marketplace architecture area include app vetting and security checks?

Yes. DARPA specifically calls out effective app vetting mechanisms, including automated code validation, security checks, and quality assurance workflows.

Are there expectations for community features and user participation in the marketplace?

Yes. DARPA is looking for community features that promote idea sharing and innovation, plus mechanisms to motivate user feedback and participation.

Are business models part of the Apps Marketplace Architecture scope?

Yes. This area explicitly explores business models for creating, sustaining, and updating apps over time.

Can the same organization build the app store and also propose to develop apps under this announcement?

DARPA includes a fairness constraint: an organization proposing to implement the app store is expected to remain impartial, and DARPA discourages those same organizations from also proposing to develop apps under this announcement.

What does the Applications Development area cover?

This AOI seeks actual Android-targeted apps that address a wide range of operational needs, with an emphasis on practical use in the field.

What mission contexts are mentioned for proposed apps?

The solicitation explicitly mentions tactical battlefield use, humanitarian assistance, and disaster recovery.

What are examples of app functions DARPA is interested in?

Examples listed include command and control, reporting, mission planning, intelligence/surveillance/reconnaissance support, real-time collaboration, geospatial visualization, analysis, language translation, training, and logistics tracking.

Are there usability expectations for the apps?

Yes. Usability is treated as a first-class requirement. Apps are expected to be simple, easy to use, and have strong user interfaces suitable for real field conditions.

What are the connectivity and bandwidth expectations for apps?

DARPA notes that connectivity assumptions vary by app, but apps that must operate over networks are expected to minimize bandwidth, remain robust despite frequent disconnects, and tolerate intermittent connectivity.

If an app needs backend or server-side components, should those be included in the proposal?

Yes. Any required server-side components or backend infrastructure needed to support an app are expected to be included in the proposal rather than treated as an external dependency.

What does the Middleware Services and Libraries area cover?

This AOI focuses on shared software components that speed development and provide common capabilities across many apps, with an emphasis on secure and resilient operation in tactical environments.

What are examples of middleware services or libraries DARPA mentions?

DARPA lists examples such as map viewing, time services, data synchronization, speech recognition, information assurance, peer-to-peer services, and app management.

What operational constraints does DARPA emphasize for middleware components?

DARPA emphasizes secure and resilient operation on tactical networks where backend computing and storage may be limited and connectivity may be unstable or changing.

What techniques are highlighted for dealing with intermittent or limited connectivity?

The solicitation calls out techniques such as data compression, synchronization strategies, prefetching, and caching as especially important.

Does the middleware area include monitoring and management tools?

Yes. This area includes tooling to monitor, manage, and analyze individual apps and the network traffic they generate, supporting both performance management and operational troubleshooting.

What does the Network Infrastructure area cover?

This AOI targets an affordable, robust, and secure mobile tactical network that works with commercial smartphones, including deployable infrastructure kits that can function like lightweight mobile base stations.

What deployment variants are envisioned for network infrastructure kits?

DARPA describes variants for fixed sites, outposts, and vehicles (moving or stationary), intended to serve dismounted users.

Does DARPA prefer commercial components and standards for network infrastructure?

Yes. The program strongly prefers leveraging commercial components and standards and aims for "good enough" solutions that can be improved with security and functionality enhancements, rather than bespoke systems that are expensive and slow to field. Commercial off-the-shelf (COTS) hardware is favored when available.

Is there an affordability target for network nodes?

Yes. DARPA states an affordability goal of roughly $5,000 per vehicle for a network node to enable wide deployment down to low tactical echelons.

Are open cellular standards or open source implementations encouraged?

Yes. Proposals are encouraged to consider open cellular standards (3GPP) and even open source implementations (such as OpenBTS).

What design trade-offs should be addressed in network infrastructure proposals?

DARPA expects proposers to explain hardware and software design choices and trade-offs, including cost, size, reach, and power.

What networking capabilities should be considered in infrastructure proposals?

DARPA encourages approaches covering discovery, control, provisioning, management, routing, and internetworking.

How important is security in this solicitation?

Security is a major theme across the solicitation. For network infrastructure, DARPA specifically calls for special attention to software modifications that address known vulnerabilities in commercial devices and wireless networks.

Are hardware modifications allowed or expected?

Hardware modifications may be proposed, but DARPA indicates they must be carefully justified and should still align with the affordability and rapid execution goals.

Is the program intended for unclassified or classified environments?

The program is primarily oriented toward unclassified environments and networks.

If a proposer wants to address classified-network enablement, how should it be presented?

DARPA asks that classified-network enablement be presented as an optional element rather than the core approach.

Can proposers submit ideas outside the four named Areas of Interest?

Yes. DARPA signals openness to related proposals beyond the named AOIs, including vulnerability analysis and security architecture, as long as the work supports the broader goal of developing and deploying mobile apps effectively in defense settings.

What is the expected pace and delivery approach?

The solicitation pushes for speed and iterative delivery, with aggressive schedules and an initial proof-of-concept demonstration targeted within the first six months, followed by continuing enhancements.

If an organization wants to pursue more than one Area of Interest, how should proposals be structured?

DARPA prefers separate proposals if an organization wants to pursue more than one AOI.

If a proposal includes multiple apps or multiple services, how should that be organized?

DARPA indicates that if a proposal includes multiple apps or multiple services, each should be broken out as separately described and separately costed tasks (or submitted as separate proposals).

What award instruments are mentioned for this opportunity?

The opportunity uses flexible award instruments, including cooperative agreements, grants, and other procurement contract mechanisms.

Is cost sharing required?

No. The solicitation states there is no cost-sharing requirement.

When was this opportunity posted?

The opportunity was posted in March 2010.

Who is eligible to apply?

The opportunity is described as broadly open to eligible applicants without restrictive categories, subject to any eligibility clarifications in the full BAA.