elective-stereophonic
elective-stereophonic
Android/Iphone App Bounty  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 [2]  All

Author Topic: Android/Iphone App Bounty  (Read 9768 times)

PhoneOperator

  • Sr. Member
  • ****
  • Karma: +15/-6
  • Offline Offline
  • Posts: 388
    • View Profile
    • MyPhoneRobot
Re: Android/Iphone App Bounty
« Reply #20 on: September 19, 2014, 11:44:14 am »

My Android wallet app project is now funded and I will go ahead with this. :-)

See: https://nxtforum.org/nxt-projects/project-ideaoffer-nxt-wallet-for-android/msg42155/#msg42155

Cheers,
Marcus


Marcus03 launched a fundraiser on AE:
https://nxtforum.org/nxt-projects/project-ideaoffer-nxt-wallet-for-android/ 

Hi!

Status: Fund raising has started and will run between June 13th to July 13th 2014 or shorter in case I feel the project is well funded earlier.

As explained here I've pulled the plug for at least 6 months, maybe longer, for my NXTSolaris client. While it is open-source and anyone else can go on with it, I'm missing the motivation to do so, since I believe that it's wesley's client that NXT needs right now.

I wrote NXT Solaris in a way to be able to use parts of the code for mobile devices and after the recent discussion about the need for an Android client, I want to offer the following project to the NXT community:



Objective

A fully functional, open-source Android NXT wallet for Gingerbread (Android 2.3.3–2.3.7), Ice Cream Sandwich (4.0.3-4.0.4), Jelly Bean (4.1.x, 4.2.x, 4.3.x) and KitKat (4.4.x) on ARMv7 devices with NEON support (see here for an incomplete list of supported devices). Transaction signing done client-side with the Android app connecting to "well-known" public NRS server without sending account secrets over the network.

Function wise, I imagine a mix between Mycelium (for Bitcoin) and wesleys excellent desktop client. Ease-of-use vs. feature overload.

The following features are planned:
 * Adding/creating multiple accounts with the option to store the account secrets in an encrypted password protected wallet on the device. Wallet backup available.
 * Support for Reed-Solomon address format.
 * Showing balances for registered accounts in NXT.
 * Showing transactions for registered accounts.
 * Contact list (account numbers with names)
 * Sending NXT
 + Support for QR codes (scan a QR address, display a QR code for an address or a receive request (address plus an amount and a description))
 + NXT corporate design
 

The following features are NOT planned:
 - Block explorer like functionality
 - Aliases (showing them, registering them, etc.)
 - Asset exchange support
 - Voting and whatever comes up next out of the core. ;-)
 - No explicit tablet support (Nexus 7/8, etc.)

 
The following features would be nice, but it's not clear yet if they can be implemented:
 O Showing balances for registered accounts in NXT, BTC, USD and EUR. Also showing exchange rates.
 O Listing in the Google Play Store as a free app (not sure about their rules yet, but this is of course vital for mainstream adoption of NXT)
 


Development Roadmap

0.) Check if I can technically compile for android (openssl libs requirements met, etc.) [DONE]
    If anyone wants to try my proof-of-concept app: https://dl.dropboxusercontent.com/u/23825856/NXTWallet/NXTWallet_v0.0.apk (this is really just a mockup for the navigation and a quick test on the "Debug" page to check if the openssl requirements are met on Android - only tested on one device and an emulator yet)

I would be starting with closed source versions running against the testnet.

1.) GUI design (what is where and can it be accessed - look and styles to be done later)
2.) Implementation of items above marked with *. (releases in-between)
3.) Implementation of items above marked with +. (releases in-between)
4.) Switching to open source.
5.) Testing, bug fixes, code review (releases in-between) - the wallet setup (encryption/decryption/adding of secrets etc.) is obviously extremely important... 
5.) Switching to mainnet.
6.) Implementation of items above marked with + (QR code support and corporate design).
7.) Implementation of items above marked with O.


ETA

This is software development - don't ask. It's ready when it's ready. A rough, pessimistic estimate would be 3 to 4 months after the start.


Fund raising

I issued the asset "AndroidCli" (Asset Id:  12414770996347165541 Account: NXT-X5EB-VSL5-Z7DU-3GWTJ ) for project fund raising and put up sell orders at 1 NXT. If you want to fund this projects please buy as many assets as you want to fund in NXT. As long as the fund raising is running you can step back from funding by transfering the assets back to the issuer account NXT-X5EB-VSL5-Z7DU-3GWTJ. I will then send the NXT back to the sender account (done at least once a day, but you might want to pm me).

The fund raising will run for a maximum of one month (June 13th to July 13th 2014), but I might decide to close it earlier if I feel the project is well funded.

If I decide the project is well funded (might happen any time I see fit or after one month latest) I will no longer redeem NXT for assets transfered back to issuer account.

If I decide the project is not well funded after one month, I will cancel my sell order and put up a buy order at 1 1XT so that everyone is free to sell the asset against my buy order with minimal loss (2 NXT in transaction fees).

Change from the asset description: The asset decription states that I would put up a sell and a slightly higher buy order during the funding phase. I had missed that fractional prices are not allowed, so if you want to step back from your funding during the funding phase, please transfer your assets to the issuer account as explained above.

Thanks for considering funding my project! :-)

Cheers,
Marcus

Let's get this, Nxters!

Even the TecDev Com and MC can support this through AE ( + get the NXT back if something goes wrong)! Interested? I hope so… ;)

So would there be a real problem with battery and 3g/4g bill even if we have rich feature client?
Logged
Pages: 1 [2]  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly