Hi Ash,
Looks like you’re doing some good work here.
You do have some tough competition however, as Uphold allow the purchase of Dash with UK credit / debit cards and bank transfer, and their UX is first class.
I like the fact that you are UK and Dash focused. I think there’s a big market to be tapped here.
I enjoyed the 4 articles on the home page. They are nicely written and will help newbies.
Couple of minor typos:
From “Crypto Privacy”
who you are or were you are from the wallet address. (should be Where)
From “InstantSend”
but it is also technically that the debit card they are using is stolen or the cash they have is a forgery. (The word ‘possible’ is missing.)
Also, the hyperlinks in the articles take ppl away from your site, perhaps you should set it so that a new tab or window is opened, otherwise you may lose visitors?
Keep up the good work.
The site and idea is nice.
All the best,
Dashinstant.
Hello all,
With two months of full-time work into the eWallet exchange application, it's time for the first update from the development team. That's just me for now due to budget constraints. Despite that, we've made good progress all round. Here's a rough breakdown of the aspects:
- Application scaffold
- Exchange rate aggregation from numerous sources
- Identity validation document upload with manual verification
- Rough exchange browser application (built with react)
- Bizops browser application
- Integration with a dash node running on the test network
- Partial integration with two credit card processors
- Utilisation of the amazon simple email service
While the actual code isn't production ready at the moment with very few tests, the above provides the full flow of functionality when using the testnet and payment sandboxes.
This means a test user can:
1) Visit our development version of the exchange site.
2) Request a new order for dash.
3) Receive a responsive email with the link for identity validation.
4) Upload KYC docs and wait for confirmation email.
5) Make a test payment with fake card details.
6) See the dash client notification that the transaction has been submitted and is awaiting blockchain confirmations.
The next month I'll be working through refactoring areas of the codebase which are not very maintainable, writing tests, focusing on how all the various errors will bubble up to the user with well written responses - essentially a lot of sanding down the rough edges and generally trying to bring it to you as a high-fidelity demo for your feedback.
We were in two minds whether to host what we have so far on an aws instance so you could have a play and recieve some test dash, however the current UI was created purely for testing.
We'd rather manage expectations for now by showing you what it will look like without functionality as opposed to a usable demo without sleek and sexy asethetics.
So that's it for my first write up, thanks for reading.
My next scheduled update will be at the end of June along with a useable demo before the August full launch.
Stay tuned,
Alex.
Do you think a dash price chart on the dashboard is best suited to your customers? Or might it better to show the customer's monthly buying and selling?
Hello all,
With two months of full-time work into the eWallet exchange application, it's time for the first update from the development team. That's just me for now due to budget constraints. Despite that, we've made good progress all round. Here's a rough breakdown of the aspects:
- Application scaffold
- Exchange rate aggregation from numerous sources
- Identity validation document upload with manual verification
- Rough exchange browser application (built with react)
- Bizops browser application
- Integration with a dash node running on the test network
- Partial integration with two credit card processors
- Utilisation of the amazon simple email service
While the actual code isn't production ready at the moment with very few tests, the above provides the full flow of functionality when using the testnet and payment sandboxes.
This means a test user can:
1) Visit our development version of the exchange site.
2) Request a new order for dash.
3) Receive a responsive email with the link for identity validation.
4) Upload KYC docs and wait for confirmation email.
5) Make a test payment with fake card details.
6) See the dash client notification that the transaction has been submitted and is awaiting blockchain confirmations.
The next month I'll be working through refactoring areas of the codebase which are not very maintainable, writing tests, focusing on how all the various errors will bubble up to the user with well written responses - essentially a lot of sanding down the rough edges and generally trying to bring it to you as a high-fidelity demo for your feedback.
We were in two minds whether to host what we have so far on an aws instance so you could have a play and recieve some test dash, however the current UI was created purely for testing.
We'd rather manage expectations for now by showing you what it will look like without functionality as opposed to a usable demo without sleek and sexy asethetics.
So that's it for my first write up, thanks for reading.
My next scheduled update will be at the end of June along with a useable demo before the August full launch.
Stay tuned,
Alex.
Thanks for the feedback - It's a good point. We've based the initial layout off of Coinbase and whilst they do many things right they're far from perfect. We'll be developing all of these as react components so we'll be able to shift them around as necessary (at some point maybe even giving the user the power to customise their dashboard).
In terms of the feedback we initially were reaching out to people with questions as we went but our thinking at the moment is as we're revising and reiterating a lot of what we're doing it makes sense to compile a feedback survey for users to complete in their own time towards the end of the initial build which will inform our layouts & offering a bit more.
On this one though, what do you think the most important components would be and what order should they be in? Here's our list thus far:
Transaction Record (Line graph)
Transaction Record (List format)
Account Holdings (Dash/Gbp, Line graph)
Account Holdings (Pie)
Account Holdings (Static Info)
Dash Value Tracker
Dash Conversion Tool
Purchase Widget
Quick thought.. do you think perhaps it would be better to market it as eWallet.uk instead of the legacy .co.uk? Obviously both domain suffixes should point to the same place, but I mean in terms of marketing. It's true not many people have switched to the newer / shorter extension, but personally I prefer the shorter extension.