Legal permission to use Bangle.js images?

[RKBoss6]

Hello! I'm getting ready to submit my open-source iOS companion app to the app store, and it asks about obtaining all the necessary content rights to use the images in-app. All my app uses for Bangle.js images is the Bangle.js 1 and 2 thumbnail pics here, and app loader support. I just wanted to check with you, @gfwilliams to make sure it's good to publish my app, so I can avoid the chance of legal troubles later on...

Here's screenshots if you want to see :)

[gfwilliams]

Excellent - thanks for checking! Yes, you absolutely have my permission to use the images in https://www.espruino.com/img, and all the stuff in https://github.com/espruino/BangleApps is MIT licensed which should be ok?

For the Apps tab have you been able to use something like https://github.com/espruino/BangleApps/blob/master/android.html to forward the communications over to the Bangle? The less duplication we have the easier it'll be to keep things working in the future.

[RKBoss6]

Ah - I have the js code (which is slightly different, since it has to hook into CoreBluetooth) auto-injected by the app as a <script> tag inside the main HTML page before it loads. That way, it'll handle all the web bluetooth forwarding to iOS APIs, and will basically work on pretty much every web bluetooth site, including the IDE and app loaders.
The extra settings are an issue though, as like android, iOS doesn't support the emulator and uploading files from the web view...

[gfwilliams]

That sounds great! Injecting code in a lot of ways is much easier than having the separate android.html.

I guess you could always inject code that hides the menu options which don't make sense?

Not sure if you've seen but I've been looking at hooking into the UART.js library for Android (rather than puck.js) at https://github.com/espruino/BangleApps/tree/Gadgetbridge-UART.js - depending how you did stuff you might find doing something similar makes things easier for you.

[RKBoss6]

I was also thinking, if it's possible to inject code in gadgetbridge, we could do that for communications on android and then just keep the android.html the same as index.html, but with limited settings, etc, that don't work on either phone - That seems like a much easier way to go about having the app loader supported cross-platform now.

If we really wanted, we could even just have global js var that each injected script sets, and that can hide/show different settings directly in index.html.

That would probably also be a lot easier to maintain rather than keeping two separate .html files that do pretty much the same thing...

[gfwilliams]

Yes, having one file would be way better than both.

As far as I remember the main reason for the separate file was the meta viewport stuff which I wasn't sure could be changed in code after the page was loaded - but I could be wrong there, or it may not even need to be different now. At the time I was more concerned with just making it work!

I guess we don't even really need to inject JS? We could just have an android.js+ios.js that were included all the time but that only actually did anything when they detected they were being run in the correct environment (or even just if the URL had ?ios on the end).

Having the JS actually in the same repo as the app loader might make more sense to ensure things were all kept in sync, since the actual API between the host and app loader is pretty basic (just RX+TX) and is unlikely to really change.

[RKBoss6]

I don't think meta viewport is needed now, as it should handle the page resizing automatically now, afaict. Having anandroid.js and ios.js would be nice indeed - it would be fabulous if the app loader could auto-detect, so it works regardless of the ?ios, which many people might not know about out of the box. Right now, I'm just focusing on having the app pass the Apple review checks though (they need a video of the communications between devices and other fixes), so as you say, right now I'm just concerned with making it work 🤣. Later on though, I'd love to make the scripts in the repo itself and consolidate the two .html files into one!

[RKBoss6]

Alright, Apple is asking for documentation that you (Espruino) has authorized me to build and publish an app for your proprietary hardware. The way that I see is either a PDF or letter of you giving your explicit approval on behalf of Espruino, and must have your name, my name, your signature, the app name (BlueWatch for Bangle.js) and Espruino contact information. Can we confer more through email about this?

[gfwilliams]

Sure! Drop me an email at gw@pur3.co.uk

Not sure quite why they need it given it's an Open Source product, but hey...

[RKBoss6]

Thanks, just sent an email your way!