2019-04-30, 10:08
you have to decide what you really want to do:
a) completely run tmm on an android device (analyzing all data on this device; store the database on this device; ...)
b) just use that device as a frontend for tmm
I suppose a) won't be implementable in a fairly amount of time, because you have to check if every used lib is available on this device too (android runs primary in arm devices whereas tmm runs on x86) and you have to re-write the whole UI
I could think of b) to be implemented (in a sort of server/client architecture), but this needs a huge refactor on the server side (what is tmm now) and needs a completely rewritten UI on the client side (could be native android/IOS or html).
due to a lack of manpower we could do at maximum to create an API on the server side to be consumed by a client interface.. but be aware - you may need to invest dozens of hours to get this done
a) completely run tmm on an android device (analyzing all data on this device; store the database on this device; ...)
b) just use that device as a frontend for tmm
I suppose a) won't be implementable in a fairly amount of time, because you have to check if every used lib is available on this device too (android runs primary in arm devices whereas tmm runs on x86) and you have to re-write the whole UI
I could think of b) to be implemented (in a sort of server/client architecture), but this needs a huge refactor on the server side (what is tmm now) and needs a completely rewritten UI on the client side (could be native android/IOS or html).
due to a lack of manpower we could do at maximum to create an API on the server side to be consumed by a client interface.. but be aware - you may need to invest dozens of hours to get this done
