Task: I was allways frustrated that such a powerfull technology as VR used only for recreational goals. However, to use it for something more meaningfull there is evident lack of controls. So why not to use familar PC controls every body used to? In this demo I work on thing that will sync your PC with VR view in Chrome for Android so you can use mouse and keyboard as ususlly.

Tech stack:

• THREE.js
• Socket.io (p2p addon)
• Webpack

Notes: To be able to move camera view you should to open the same page on your mobile device.

Date: Currently under construction

Task: create a SPA with suite of diagrams. User can click on diagram and open it's full-size version. User can change title of diagram or axis. SPA should contain "help" section.

Predefined tech stack:

• Backbone
• Require.js
• Grunt
• Highcharts

Notes: I made application with something big in mind. Therefore user can load "suite" – a set of diagrams and dataset separately via network (in examples used GitHub API). I focused on scalability and maintainability, therefore I added few additional layers of abstraction, e.g. drivers for visualisation libraries - in case if it will be decided to switch to D3 or something once.

Cool stuff: Help page is written in markdown and compiles to HTML in browser.

Design: mine, inspired by Material UI

Date: Feb, 2015

Task: create a SPA that will get from specified API list of files and show them. User should be able to sort files by date, size, filter them, enter folders etc.

Used tech stack: (no predefined requirements)

• React
• Flux
• Browserify
• Gulp
• Babel
• Jest

Notes: In this assignment one of the main problem to solve was to pick the tech stack. I used React/Flux based stack because there was no obvious controllers but obvious components and it looked that there was no need for two-way data binding. I was very satisfied with this decision and this stack (with Redux and Webpack instead of Facebook's Flux and Browserify) became my favorite. Only Jest was a nightmare. I never tried to use it sice that.

Cool stuff: Mocked API was generated with api-mock library by apiary.

Design: mine, based on Material UI

Date: Apr, 2015

Task: create a SPA that will show issues from selected github repo using public github API. It should use browser history (via hash) have pagination etc.

Used tech stack:

• Backbone
(Predefined)
• Gulp
• Karma + Mocha + Chai

Notes: This assignment was focused on robustness and stability, so I spent significant time hunting bugs and stuff. One of the main requirments was use as few third party libraries as possible. App also "should not be another standard Bootstrap app" so I created look and feel from scratch but with inspiration in my favorite Google's Material UI. Taks-giver also asked not to publish sources in public repos.

Design: mine, inspired by Material UI

Date: June, 2015

The very first prototype of what later became Skem.io (see projects section). In this app user can place onto workspace React-Bootstrap components, extract parts as a new components, edit styles and properties of components. Finally, whole app and its components can be "exported" as JSX billets.

Used tech stack:

• React
• Browserify
• Gulp
• Babel

Cool stuff: When I started work on Skem.io I had to throw away almost all code from this prototype.

Design: Bootstrap

Date: June, 2015

Task: create a calendar app using .psd mockup. User should be able to add, remove, expand events. Events should not been removed after page reload.

Used tech:

• KnockountJS

Cool stuff: It was the simpliest test assignment. I even didn't use in it any dependency management system.

Design: provided in task

Date: Apr, 2014

The first version of Skem.io is basically an graphical user interface upon React with built-in visual functional programming language which is compiled to javascript and adds custom logic into components. User can create application, views and components; add elements into them, edit their appearance, using CSS WYSIWYG editor; compose logic schema of components manipulating function blocks and connecting them with wires.

Tech stack:

• React
• Redux
• Babel
• Webpack
• Karma-Mocha-Chai

Design: mine, Bootstrap (SpaceLab), A. Sidorov

Date: Jul, 2015 – Feb 2016

In second version of Skem.io we got rid of visual programming language (because it turned up that it is still too hard for end user). Instead we added an interface for Redux data flow and make everything working at the same time and place where user edit it. There is no public preview yet but there is a teaser demo video.

Tech stack: mostly the same

Design: UX mine, design by A. Sidorov

Date: Feb, 2015 – May 2016

The library to render tree structures on a canvas in a declarative way. You just feed to the library object that looks pretty similar to DOM and canvas will draw that object every time. The nodes of that object contains "geometry" - the function returning Path2D, styles to be applied and event listeners. The library was developed for Skem.io visual programming language editor.

Date: Feb 2016

Scilance was intended as freelance platform and kind of social network for scientists and engineers. It was my first big internet project because of which I came into industry at all.

Tech stack:

• PHP
• CodeIgniter
• MySQL
• jQuery

Design: mine, inspired by LinkedIn (of that time)

Date: Dec, 2009 – Jan 2012

Later I realised that freelance in projects that involves serious R&D is not very desirable thing, I tried to pivot the platform towards something like expert bank. It was my first SPA, by the way, based on my own MVC jQuery-based framework (yes, I tried to reinvent BackBone ☺️).

Tech stack: mostly the same

Design: mine, inspired by Clarity.fm (of that time)

Date: Jan, 2012 – Jun 2013