Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!
+01 (414) 230 - 5550
Dariusz Pieńczykowski, Technology


The first day of the workshops. On the first day, we had workshops about basics of react-native. Three guys: Mike Grabowski, Michał Chudziak and Nader Dabit lead them. They gave us useful advice about best practices, how to order static methods of JS files and conventions about naming folders and splitting them well. While talking about expo, routes, styling and writing unit tests as well as e2e, they helped everyone with kindness and calmness. The workshop had some elements for everyone. It helped beginners to start native adventure and also standardized knowledge as well as gave some new information including tips for people working with it.


The second day of the workshops. On the second day, there were two paths of workshops. I chose navigation workshop and animations. On the first workshop, I heard about available navigations in the community, about a difference between those and which one is better to each app. Workshops were lead by Ferran Negre Pizarro & Raúl Gómez Acuña who had excellent knowledge in this topic. On the workshops, we created the same project using react-navigation and react-native-navigation. Both are good in use, but for me, better, easier and more comfortable is react-navigation. We learned how to style application header and buttons for navigation. Workshops were more technical than the day before and many people got lost. A helper for them was a repository with code created by workshop presenters. The second workshop was animations lead by Jani Eväkallio & Phil Plückthun – very good, funny and optimistic guys. On the workshop, we were implementing animations for the app created by leaders. In the meantime, leads were asking people questions about ideas how to fix issues connected with animations in apps.  For me, it was the best workshop I have ever took part in due to the way they were guided, professionalism and because I’m very interested in this topic.



Conference 1st day On the conference, I heard a lot of interesting presentations. I don’t want to describe each of them, I’ll just write a quick brief about what I saw and heard. Presenters gave me a lot of interesting pieces of information about RN, JS and Native. They talked about their experience with giving good examples and hints. They showed me how to build a simple application using Ignite as starting template for RN, they talked about the Facebook engine – Yoga, the difference between web dev,  react-native and art. They also shared their ideas about connecting react-native with Raspberry. I heard about new improvements in starting developing like Slack RN or They mentioned solutions for debugging performance and memory. I learned how to build new plugins for RN and style it using better plugin than StyleSheets.create. Here are the most exciting (for me as Frontend developer specialized in styling) information/things that I’ll remember from the conference:   The day finished with the evening party. It was great. Nice and beautiful place, skewers, sausages, beer and drinks for free for everyone. I had time for talking to others and spent nice time with the react-native community. I listened people from other companies, as they were talking about their own projects, happiness and sadness.


Conference 2nd day On the second day, the conference was started by a guy from FB with an interesting presentation about animations and hacking them. After that, I heard about cross platforms using RN and options for RN – Weex and Flutter, about good replacement for JS language – oCamel (ReasonML) because it’s written in meta native. Networking and connecting things with the Internet. The offline version of my app using redux. Implementing payments on RN in few minutes. Snapshot plugin for multiple simultaneous simulators and generating screenshots for iOS. And many, many other things which were interesting more or less, but still, interesting on QA session as the last point of the program.Me with Mike Grabowski – conference conceptor and Co-funder at   I’m very glad I was at this event. Everything was buttoned up. It was fascinating and even better motivated me to work. I hope, next year there will be a continuation of it ;)


Dariusz Pieńczykowski, Technology

If you are a web developer or a businessman, wondering what web application to choose for your specific needs, take into consideration Angular.js. This open-source framework, supervised by Google and individual or corporate development teams, can be used to simplify the development and testing of single-page applications. Angular.js developers use it for building dynamic mobile and desktop Web applications to accomplish their tasks in the best possible way.


Many developers decide to learn and use Angular.js because this framework allows them to use HTML as a template language and then develop its syntax to express their application’s components clearly. Angular.js developers state that what saves their time is the Angular’s data binding and dependency injection solutions. Further, they explain that as a declarative language for static documents, HTML brings about much effort to solve some impedance mismatch between dynamic applications and static documents. Therefore, Angular.js developers introduced a construct called directives to teach a browser new syntax, and this way minimize the discrepancy occurring between document centric HTML and time consuming steps to create new HTML constructs. The directives introduced to Angular. js by developers include,

  • Data binding

  • Document Object Model (DOM) control specifications for repeating, showing and hiding DOM elements

  • Support for forms and form validation

  • Adding new behavior to DOM fragments, such as DOM event handling

  • Grouping of HTML into reusable components. (AngularJS Guide, 2016)

Thanks to many good solutions, Angular.js developers get full control over the initialization process in automated tests. For example: A developer can load only necessary services and successfully perform automatic tests using the separation feature module. Besides, if following “one file – one module” principle, they do not need to remember module loading order.


Concluding, we want to signalize that because of its large community (the core team members and many contributors), the Angular.js open-source framework has been evolving dynamically. A lot of Angular modules can be found at the Angular Modules website (most popular include AngularUI for AngularJS, Angular directives for Twitter’s Bootstrap, Angular authorization, and restangular). So, why not to choose Angular.js for your next project?