# Do I really need to call initialiseJUCE (Context appContext); on Android?

**URL:** <https://forum.juce.com/t/do-i-really-need-to-call-initialisejuce-context-appcontext-on-android/46020>\
**Category:** Android\
**Created:** [May 14, 2021, 7:06pm UTC](https://forum.juce.com/t/do-i-really-need-to-call-initialisejuce-context-appcontext-on-android/46020 "2021-05-14T19:06:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![guerlando](https://avatars.discourse-cdn.com/v4/letter/g/db5fbb/32.png) [@guerlando](https://forum.juce.com/u/guerlando)\
**Post date:** [May 14, 2021, 7:06pm UTC](https://forum.juce.com/t/do-i-really-need-to-call-initialisejuce-context-appcontext-on-android/46020/1 "2021-05-14T19:06:32Z")

</div>

This is how Juce is started on Android:

```
public native static void initialiseJUCE (Context appContext);

```

This calls

```
void Thread::initialiseJUCE (void* jniEnv, void* context)
{
    static CriticalSection cs;
    ScopedLock lock (cs);

    // jniEnv and context should not be null!
    jassert (jniEnv != nullptr && context != nullptr);

```

which ensures `appContext` is not null.

I would like to use Juce through Flutter, suing Dart’s FFI. However, I cannot use FFI to start Juce because Dart has no `Context appContext` to call the lib directly. I end up having to rely on java to load the lib, and then I’m stuck having to write proxy functions from java to C++ for every juce call I want to do.

Is there a solution for this?