An update from us:
@GodTanu raised some questions in the DAO thread where I expressed my dissatisfaction with the NCF, so I wanted to take this opportunity to provide an update with LocationCore now the NCF has been concluded.
Like many projects here the NCF provided us a way to kickstart development of our systems on NEM, it was something we were glad to be a part of and in our case especially helped âgrease the wheelsâ for other executives to get on board with using NEM as a platform over other solutions.
We didnât provide too many community updates, it is of no secret that we were distinctly unhappy with the process and lackadaisical attitude of the NCF through its various incarnations. However to face the criticism straight on about why it has seemingly taken a year to produce anything - please find attached an update from us:
The total time for development was approximately 6 months from the beginning of May:
Following multiple delays in receiving funds (or really any kind of communication) after the community vote and the subsequent tanking in XEM price (Vote finished Jan 25th (XEM = ~ 1USD) - payment was made on March 14th (XEM = ~0.45USD) ), this now already represented less than half of our expected funds.
We executed developer contracts soon after the amount was received - Developers started in June (as they were completing other projects). Development for iOS was completed at the start of December (The SDK was done in October), Android was pushed back to focus on other work in light of the continued price drop of XEM.
Our Team and Developers decided it was more efficient to complete each platform as a single package (iOS SDK + iOS Application / Android SDK & Android App) hence why we didnât submit Milestone 2 - Business doesnât go in a straight line.
We contacted NCF on 14th January 2019 to say we were ready to submit proof for our milestones - so all in around 7 months (June -> January) to submit Milestone 1 and Milestone 3 including the Xmas and NY break.
There were several reasons for the extra months delay vs our 6 month plan but they mostly came about from back and forth with Apple about an AppStore listing & it falling over Christmas and New Years where many developers took time off.
Due to new AppStore rules - Apple will not accept the application to the app store (Part of Milestones 3 requirements for acceptance) without a âtangible use of location dataâ, they didnât accept LocationCoreâs premise as being âtangible useâ (?) meaning we would have to put some kind of pointless map on the application in order for them to accept it on the app store. Unfortunately this is the reality with Apple and something we expect many other projects will come up against. However this was more development that was adding no value to the LocationCore product whatsoever, only costing us more money, by this point NEM was worth so little (~0.04 USD) we decided to just keep on developing the ecosystem around LocationCore (Milestone 6 & Milestone 7 in our proposal - These are now completed minus the blockchain integration - see screenshots below).
We have used over 250K USD of our own money to fund the development around NEM - the likelihood of getting any kind of meaningful reimbursement from the XEM we have been given so far from the NCF seems unlikely for the foreseeable future with the price as it is.
Now, with the withdrawal of the NCF and Catapult STILL not ready on the public chain there is little impetus for us to consider re-starting the LocationCore development as our proposal lists it.
This doesnât mean the project is dead - it simply means we will not be putting in effort to âFulfillâ the proposal milestone requirements unless they fit in with our core business & customer requirements.
So here is what we have completed:
LocationCore app on iOS & SWIFT 4.2 SDK for NanoWallet compatible wallets and various transaction functions (Iâm waiting on go ahead to release the SDK code to our public Github)
This is an older photo sorry - I donât have a recent one but the new one looks much sexier!
Lambda functions to handle the âShared private key / trusted nodeâ problem when sending transactions from Mobile devices - this ensures high availability rather than trying to maintain a specific node just for this function (Again waiting on go ahead to release to our public Github)
Testnet addressese we were using to verify functionality:
http://testnet-explorer.nemtool.com/#/s_account?account=TDAPZIZRCWXHSGJHUYYVKQWGRSN4R3TCTL44K4EK
http://testnet-explorer.nemtool.com/#/s_account?account=TA4HBXROKPS7W7OKZD2XXEEXGN4MOY7LKKTD2D77
LOCALLY (now rebranded from Digital2Go) now has a product called Discover, this was created as part of the work we were doing for Milestone 6 & Milestone 7:
We currently process over 1B records per day and have a data warehouse of over 40B records, we provide âaccessâ to this data to allow our customers to create their own audience segments. The payments are currently made in âCreditsâ from Fiat, but this was designed to hook into several payment methods - including cryptocurrency.
Some screenshots from our Staging server:
And this is really just the tip of the iceberg, I hope those of you who are technical can appreciate the level of infrastructure that has been built to implement all of this.
I will send a further update once things settle on our side - we are very busy bringing these new products to market (including LocationCore / LOCALLY Reward).
Thanks all!