🗞 NEM Authenticator - News 🗞
The development of NEM Authenticator is stopped, the reason is that NEM Authenticator has a strong dependency of nem-library, which it was part of NEM Framework.
Because of this, we decided, @guillemsc and I, implement a first nem-library by our own to accomplish the best results with NEM Authenticator, NEMPay and further projects.
Today, nem-library has reached a important milestone, so we are happy to announce that NEM Authenticator development will start again the next week !! 😁😁😁
I have a problem with update NEMPay.
App is downloading up to 97% thereafter stopping and i get error "there was a problem parsing the package". What is the cause can be? I have been reinstalled Beta.(Android 4.4.2)
hello @aleix_mp, should i use this group if i intend to launch a beta test of a project? would be waiting for some more joins but in a few days my project is ready for it.. so want to make sure if i can use this group for a first "semi public beta"
At the moment, we have decided to limit installations to API 21. To ensure it works with lower versions, we have to study the possibility to add 30MB of an embedded browser to the base application.
I'll keep you posted.
NEM Pay is mosaic centered while NEM iOS Wallet is XEM centered.
Currently we are taking into account diferent divisibilites, or even sending levied mosaics.
The app aims to encourage companies and organizations to adquire their own namespace and mosaic, having a custom app to start taking advantadge of NEM blockchain.
Other common use case would be fork NemPay to be used as a base app for creating a blockchain app, cutting cost significantly, as a significant part has been done and the same code compiles for Android and iOS.
Furthermore, we are trying to do our best to remove difficult concepts from NEM Blockchain and present them in a different way so final users don't even need to know that they are using the blockchain.
For example, for a non expert on NEM user, there is no need to have Harvesting, multisig and encription capabilities, or the need to indicate which node should select to use the service.
OMG, this is EXACTLY what I've been telling my staff. I have my team developing reports on ICOs and other digital assets and I said that my great grandmother MUST be able to understand what the asset is. I believe that is the BIGGEST thing holding back the growth of Digital Assets. It's too complicated to use without taking some classes. XEM WAS like that for me at first but now that I know it, I love it. When our site opens, XEM will be our main payment source. Just trying to work out how to create a subscription for my website subscribers.
I'm not a programmer (anymore) and frankly, have lost many of my skills because I - well just don't use them anymore. The tech has grown so fast that I fell too far behind.
I mean, the Mosaic's and Namespace stuff you mentioned just sounded like a different language to me.
What I'm hoping to do it make it so that grandma can understand what XEM is and become an asset user / holder.
After updating, create a transaction.
Then, the screen of NEM Auth becomes pure white and the transaction is not displayed.
Possibly, I selected NEM Auth from Android application list.
Deleted data and cache from storage.
After redoing from the secret key input phase, it worked normally.