C++ development
C++ comes in when performance matters more than convenience: image processing, audio, and libraries shared between Android and iOS at the native level.
std::cout << "Hello, Paris\n";How we use C++
Some features cannot afford the overhead of a managed runtime, such as real-time image filters or decoding damaged barcodes from a blurry frame. For these we write focused C++ libraries and expose them to Android through the NDK and JNI, and to iOS through a thin Objective-C++ bridge. One library then serves both platforms with the same behaviour. We keep the C++ surface small, cover it with GoogleTest, and profile it on real low-end devices rather than only on a development machine.
What we build with C++
- Performance-critical modules for Android and iOS
- NDK, JNI and Objective-C++ bridges
- Image and signal processing with OpenCV
- Cross-platform builds with CMake
- Profiling on low-end hardware
Questions about C++
Does writing native C++ make an app harder to maintain?
It can, so we limit it to the parts that need it and keep a clear interface around them.
Can one C++ library really run on both platforms?
Yes. The same source is compiled for each platform, with a small bridge on each side.
Discuss a C++ project
We reply from [email protected]. Send any documents to that address after your first message.