VB.net develop for online stock/share purchase and sell

Job ID: 39640520

Budget: €250 – €750 EUR

I'm seeking a dedicated professional to create an EXE stand-alone applications using VB.NET only.

The creation of a new VB.NET application from scratch is required.
No C#, no PHP, no Python, no Java, no third party controls, no compiled objects.

The use of free objects/sources freely available on the internet is really appreciated (and reduces testing and development time).


----- The goal -----
Stock exchange data display.
I'm looking for a VB.NET programmer who can "call" the API and/or WebServices of a provider/broker to:
-Get real-time quotes (about 2 per second) and draw a graph in the form
-Buy and sell indexes/stocks selected

The application must be able to carry out the process of buying and selling stock.
The choice of broker is up to the developer (Forex, eToro, Trading 212, Capital.com, Plus500, Interactive Brokers, DEGIRO, AvaTrade, ...)


----- Layout -----
Application layout is easy: one form only (because must be stand alone)
The important thing is that the information of these 4 indicators is displayed: ADX, MACD, RSI 14, Stoch RSI

It would be useful if the form displayed the chart of a stock (e.g. Microsoft Corporation, code MSFT) --> https://it.advfn.com/mercati/NASDAQ/MSFT/grafico/streaming
or an index (e.g. S&P 500, code SP500) --> https://it.advfn.com/mercati/SPI/SP500/grafico/streaming
reading data that changes.
Alternatively, could be used API of Polygon.io (but is not for free) or any other financial website of your choice, that can show real-time values. REAL-TIME.

I suggest the adoption of free objects for displaying the received quotes, such as
https://github.com/DevExpress-Examples/winforms-chart-create-candlestick-chart/


----- Performance ----- (!!!!)
Performance is extremely important as data changes very quickly (at least 2 times per second) and a slow read or adopting objects that slow down the process... is a losing choice, which makes the application unusable.


----- Application tests -----
To carry out the development, (if necessary) the programmer will have to create his own accounts on providers, which will then be used by me for testing.


----- System and database -----
If a DB is needed, we need to use a "local database"
We prefer to use "MS Access" 97/2000 DB (.mdb). Application will be tested and used into an Intranet.
The application will work into an intranet (not reachable from the internet).


----- the Logic -----
Give us the chance to implement application logic: when a value is received (event-driven), when the combination of 2 or 3 or 4 graph values is xxxx, etc.
In the source code it is necessary to use a good level of commenting.


----- Costs and quality -----
Please pay attention on application performances (see above).
Please, no ask me «what is your budget for this project?»
Bonuses provided at the end of the project for compliance with the timing and quality of the software.

No upfront. No payment before successful completion of all tests.
Source-code required (daily!) for my test. No compiled.
Unnecessary images, files, libraries, ... must be removed.


----- Source code and Log -----
The source code is required to have a good level of comments, to allow bug-fixing, code maintenance and possibly future evolution.
The source code must be written clearly, without adopting complex structures that make interpretation and maintenance difficult. The team reading your source code isn't very knowledgeable about .Net, so any misunderstandings or complexities will increase the testing time.

A robust LOG showing all phases is required for the test phase: start... started, reboot... rebooted, sent request... received answer, calculation start... calculation completed, ......
This must be visible in the form and stored in a TXT file every EOD.


----- Timing -----
Proposals from programmers who do several activities in parallel will not be accepted: the quality of work could be low.
Start as soon as possible - daily update is requested (showing progress), to avoid time loss and misunderstandings about requirements.
The daily update includes sharing the sources and all the files needed to test what has been created (images, DB, accounts, ....)
Without daily update with project progress, project will be un-assigned, without exceptions