I have an application that is built with a low code framework for Android by Cellica.com. I have been asked to modify it so that it gets the higher precision Trimble catalyst GPS reading rather than the lower resolution reading from the Android device.

1st is this plausible?

2nd what do I need to do to enable my Cellica.com created app to get the reading from the attached Timble device?

Looking a the SDK documentation briefly I can see there is a two-step process, step one authenticate the app with Trimble web service to obtain a token. Is this token then used in the application call to the SDK, however, I am unclear as to which function/method i need to call?

From what I see there this is is mainly around smart database syncing - so that you (as an application developer) don't need to care about splitting db updates into small pieces, com channel security etc.

So I haven't looked into this in details - but looks like this.

I also see in the FAQ that they can handle 'locations' - although just Lat/ Long without any meta data. So pretty raw.

I have NOT seen the actual Android product (if its java, html5/ java script or something else) - but I guess you can tie a couple of things together so it works here.

So a native Android java application integrating Catalyst plus their DB connector - I would also guess this is the default use case (but just a guess).

Therefore:

1. Is it plausible: yeah, I think so, but to be sure someone would need to double check with them how their db connector actually works.

2. Under the assumption that applications developed via 'Cellica.com' means they have their database syncing component added you would just integrate the SDK OR consume TMM mock locations (and have a look at location extras) and store the value in the database fields 'monitored' by the Cellica component.

On the second topic of your question - the token question:

For each web service hosted in Trimble TPaaS (a set of web services provided by Trimble,API Cloud) the application needs to get white listed to avoid denial of service issues. This also means that you get a token at some stage - in Catalyst after logging in - to actually use those web services. Thats sort of normal for web services.

As a Catalyst developer we (TMM) handles all this for you; the only thing you (as the developer) care about is the application GUID (a unique GUID we provide to you at some stage).

You need to tell the SDK your GUID as we will use it to verify the application and e.g. download a access token for all needed web services on your behalf. So the whole token handling is moved into TMM to make this as easy as possible while keeping a certain level of security in place.

The docu mentions the token to get an idea of the full system; as a developer you only care about the GUID and few other bits and pieces that we need for fingerprinting your application.