Разработка

FrontEnd


Andrey Vaganov
Senior front-end developer @ Aggregion
Kazan

- Show main ideas of Angular 2

- Real work examples

- Redux with Angular 2. Why it's cool and easy?

- Functional reactive programming (FRP) with Angular 2

- Quick start with all of this


Nikolai Chubarov
@ Castle
Samara

Offline Mobile JS application in the browser and how to work with it:

- Functions

- Data storage

- Caching

- Updates

- Browser support


Arthur Esсhenbrener
Architect @ Megaplan
Moscow

1. How bad it was: complete absence of backend-frontend protocol, lack of auto-documentation, and many different parts of the system that had to be maintained separately.

2. The choice of the ‘point of truth’ – backend.

3. Backend uses PHP, and therefore, it is necessary to teach it the strict typing of entities - all that endpoints return should be entities expressed in the form of a class in PHP with typification in the form of annotations to the fields.

4. Static class analysis and generation of raml descriptions

5. Generation of the typescript scheme by raml description to be used on the client side.

6. To show how it's great when changing the data scheme without any respective edits on the client side breaks the compilation.



Pavel Silin
Frontend Developer @ Devim
St. Petersbourg

1) overview of different approaches to application architecture;

2) typical errors, problems and sufferings in complex react applications;

3) how to suffer less and make a scalable and supported react application.


Igor Sheko
Front End Developer @ Voximplant
Moscow

- I'll tell you what Acelerated Mobile Page is. Why it is that relevant and mega cool now.

- I'll tell you about the experience of implementing AMP in the world: what are the prerequisites for implementation, what resources are involved, what it brings in the end.

- I’ll give an overview of AMP tools and components available. And show the examples of use for the most important of them.

- I'll tell you about my own experience of implementing AMP on working projects. I'll describe a few of the most common mistakes.

- I will touch upon the topic of motivation of partners and superiors to allocate resources for the development of AMP extensions.

All the sources will be available to the listeners by a QR code on the last slide.


Alexey Zolotykh
Frontend Developer @ Wrike
St. Petersburg

I think that the report will be useful to the participants of the conference. The fact is, any successful web application requires constant improvement and support, and it's quite difficult to do it on the frontend. In other words, everybody works with legacy code on the frontend, but there is no information how to do it.

It happened so that I had to change the assembly system for the company where I am currently working (Wrike). At the moment, there are more than 2,000,000 lines of code in our frontend repository. This report was born out of the experience with this array.

1) Refactoring definition;

2) Correct refactoring, when it is necessary to refactor and when it is not;

3) Refactoring and built-in IDE and editor tools;

4) Refactoring from the console, working with the source code as the text (grep), pitfalls, ideas, solutions;

5) Refactoring of styles. Pitfalls, ideas, solutions;

6) JavaScript code refactoring using JavaScript;

7) Gulp with the save.


В докладе будет представлен подход к автоматизации процесса тестирования верстки. Разработанный внутри компании SmartHead прототип продукта позволил снизить затраты на подготовку к тестированию и минимизировать рутину. Таким образом, результат тестирования стал более качественным, а процедура легко доступной всем участникам команды разработки, в том числе и фронтенд разработчикам.


Artyom Dikmarov
Design integrator @ Simtech Development
Ульяновск

Почему не стоит использовать самые последние фреймворки и библиотеки?

Почему у самых популярных e-commerce площадок такой отсталый и некрасивый дизайн?

Что такое "Американский фронтенд"?

Как стоит верстать огромные площадки (С 10+ тысячами клиентов)?

Личные примеры, метрики и многое другое.


Pavel Silin
Frontend Developer @ Devim
St. Petersbourg
Development of React Components
of Голосование

1) using SOLID principles for react components;

2) using a stroybook to design react components;

3) as we divide the application for react components;

4) dull and smart react components;

5) react components and styles.


— избавляемся от проблем на входе, а не на выходе

— верстка - это будущий сайт, а не psd -> html

— рост качества через понимание задачи

Тестирование - поиск и исправление ошибок. Это борьба со следствием, а не с причиной

Причина - восприятие задачи по верстке исключительно как техническую.

Проблема - специалист часто делает верстку, но не сайт для пользователей.

PixelPerfect - не нужен! Наложение - не нужно! Верстка ради верстки - не нужна!

Идеальный мир - крутой верстальщик, но их единицы. Реальность - рутинная проверка и 10 итераций списков доработки. Нужна золотая середина.

Выход - коммуникация верстальщика с дизайнером и менеджером, стандарт верстки, базовый фреймворк, человеческий чеклист