Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a47d6ed7 authored by Vince Harron's avatar Vince Harron
Browse files

Clarified recommended use cases for NDK. 

Added - "game engines" officially supported use case for NDK
Removed - "self-contained" ambiguous in general and confusing to someone who is trying to do game development in C++
Removed - "that don't allocate a lot of memory" game engines do allocate a lot of memory.

Change-Id: I098de65bf0c4b4ab4a85611426b68613692e52c5
(cherry picked from commit 8da272f4)
parent 039bd508

docs/html/tools/sdk/ndk/index.jd

+2 −2
Original line number Diff line number Diff line
@@ -245,8 +245,8 @@ This is the Android Software Development Kit License Agreement 
  but it always increases your app complexity. In general, you should only use the NDK

  if it is essential to your app&mdash;never because you simply prefer to program in C/C++.</p>



  <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't

  allocate much memory, such as signal processing, physics simulation, and so on. When examining

  <p>Typical good candidates for the NDK are CPU-intensive workloads such as game engines,

  signal processing, physics simulation, and so on. When examining

  whether or not you should develop in native code, think about your requirements and see if the

  Android framework APIs provide the functionality that you need.</p>