m-apps:locAR
If you have questions of your own regarding the use of m-apps:locAR send them to support@m-apps.com making sure that you have the string "m-apps:locAR" somewhere in the subject line (otherwise your email will be 'spam filtered' out!). It also helps if you can include the version number of your installed app (shown when you start locAR) and phone type (Android+make/model,iPhone) in your message. However, please first check that you have thoroughly read the Online User Guide and other FAQs.
Also note that we would much prefer to share any explanatory response with all users (either by clarifying the relevant part of the Online User Guide or by adding to this FAQ) so please don't expect a detailed individual reply every time.
Are there any charges for using m-apps:locAR?
m-apps:locAR is highly dependent on a server network for much of its operation.
There are no charges for using the 'non-team' functions (creation/editing of nodes, viewing via Google Earth, etc)
but it is necessary to meter and apply charges to those 'team' features which make the most demand on the server network.
It is felt that a metered, 'pay as you go' charge is fairest for this type of application (at a rate of just a few (UK) pence per hour spent in a team). The 'paid for' version of m-apps:locAR includes a 50 hour 'team credit'; the 'demo' version includes 5 hours team credit so that you can try out all of the team functions before purchasing. Don't forget that this is metered time actually in a team (not elapsed time since you installed m-apps:locAR!) so a 50 hour team credit will last 50 days if you are in a team for an average of 1 hour per day.
As m-apps:locAR has only recently (2010 January 1st) been launched there are likely to be 'issues' to sort out as loading on the network increases. Metering will be suspended while any team-related functionality issues are sorted.
The means of obtaining further team-time credit will be announced soon. In the meantime, enjoy m-apps:locAR and please bear with us as we sort out any 'teething troubles'!
Why is there a limit on team size?
The number of members within a team is currently limited to 10 in order to keep network loading manageable.
Each time a team member's navigation data is updated (every few seconds) a message must be sent to every other team member plus (if base transmission is enabled) the base server. This, of course, must be done for each member of the team. Therefore, the total number of messages is related to the square of the number of team members.
For a team with two members only 4 messages have to be sent on each update (one in each direction plus one from each to base). However, for a team of 10 members up to 100 messages must be sent. A team of 20 members would require up to 400 messages for each update!