Andrius Janauskas on React native developmentLead Software Engineer @ Qoorio3 months ago
One of the challenges with react native development is dealing with current architecture of communicating between JS and native threads. This talk by one of the react native engineers gives insight into new architecture being developed by Facebook and how it might solve some of the issues commonly faced by developers.
React Native's New Architecture - Parashuram N - React Conf 2018

No comments yet
Be the first to comment

Download Qoorio to comment, talk & learn
Learn more by discovering other insights
Andrius Janauskas on React native developmentLead Software Engineer @ Qoorio3 months ago
Great news for all react native developers: authors behind reanimated library have announced major new version. It makes writing animations for react native apps much easier for the developers, but the real reason to be excited are the huge performance benefits promised. New library is written utilising new Javascript interface and is not using bridge calls at all. Animations written in javascript are executed and initialised synchronously on native side. This is groundbreaking stuff in my opinion. Check out full medium blog here:
Introducing Reanimated 2 - Software Mansion

Justas JanauskasCEO @ Qoorio
Hope Qoorio will benefit from it soon!
Karolis Grigas on Web developmentFront-end developer, team lead, dancer3 months ago
Current most popular way of developing web - React - is not sustainable. And that is a sentiment shared by React dev team (@dan_abramov at and a great article at It's interesting that web development is going through a common phenomenon of circling back into old truths and a lost way of developing software. Client-side only applications are not sustainable, slow, and are only trying to emulate what a simple static html file with some styling and javascript sprinkled on top does. But it never will, purely because of the overhead of running the code, whose results should've come from backend in the first place. And that goal - static html with javascript small enough to fulfill interactivity on the open page - sounds eerly similar to how web used to be developed 10 years ago. Output some html, and manually write javascript for that page in particular. Very performant, but equally fragile and unscalable when it comes to complexity. Meanwhile, the modern tooling and developer experience for managing complexity is absolutely great. So joining these two things together sounds like a positive direction. Our web applications should serve the results of running it as the main response, with minimal post-processing needed. It should serve minimal javascript for that page, and that page only. Browsers know how to navigate, and they do it ridicilously well. At the same time, from developers experience application mental model remains what it is now - application is one, sound, and non-leaky model which can transition and resume it's state and any point, broken down into components with the same properties. It's just that these components don't return complete representations of themselves, but only minimal result in form of html, with minimal interactivity in form of javascript. The future sounds exciting.
Second-guessing the modern web -
Vytautas Galaunia on DevelopmentSoftware engineer @qoorio3 months ago
Using Xcode? xcrun simctl delete unavailable Could be helpful, I personally regained 20Gb of disk space
Donny Wals @ 🏡 on Twitter
Mindaugas Jankauskas on Product DevelopmentProduct professional, Technology enthusiast, Product management consultant3 months ago
One of the most common challenges I noticed in Product management is being able to plan, communicate, and get buy-in from different levels of stakeholders efficiently. As Product Manager, you will have different levels of stakeholders: ▪️Company management ▪️Other PMs ▪️Your own team All of them need a different level of detail and most likely from different angles. Knowing that you might want to organize your analysis, planning process, and communication in similar structure. 🔹 Insight #1. Starting your product development planning from the top will help to focus on the most valuable problems and get management buy-in before you even start development. 🔹 Insight #2 Limiting to right level information for the right stakeholders will improve communication clarity.
Mindaugas Jankauskas on Product DevelopmentProduct professional, Technology enthusiast, Product management consultant3 months ago
Good product management is a balance between three bigger skill sets: 🔹Craft (methodologies, decision making, prioritization, routines) 🔹Communication (Company, Stakeholders, Team) 🔹Commercial awareness (Knowing problem area, understanding users and potential impact to overall business) This simple framework can actually help to structure personal development and help managers to guide Product people towards faster growth. ℹ️ In fact, this framework can be used for almost any position (be it engineer, salespeople, marketing, …) however requirements and actual skills in those sets would be different.
Mindaugas Jankauskas on Product DevelopmentProduct professional, Technology enthusiast, Product management consultant3 months ago
Have you ever been in a situation where you tell a person what you need, he confirms that he understood and when he delivers it is not exactly what you needed❓ It is a common problem in product development when user needs and perceived needs are actually different. However, there are ways to avoid situations like this: 1️⃣ Identify user needs not only by asking what he needs but by observing and understanding what he needs to achieve. 2️⃣ Visualize the result before starting working on it and discuss (wireframes, user flow diagrams, simple drawings, prototypes) to confirm that this is actually what he wants, text might not be enough. 3️⃣ Iterate, get feedback, and observe your user with the new feature. One of the methodologies to find a solution to bigger user problems is Design Sprints. There are more, and even these three points might improve the situation a lot.

Mindaugas JankauskasProduct professional, Technology enthusiast, Product management consultant
You are right Design sprints work well for bigger problems where you either not sure of all problem aspects or there are multiple possible ways to approach it. And by definition it is meant for bigger changes as it takes time and effort to organize well. However in this post I mentioned it only as an illustration that people think of different ways to make sure they understand their users before building something. Even small double-checks and feedback loops might go a long way to save time ...
View 1 more comment
People are increasingly switching their careers to the IT field, especially programming. 💻 Oftentimes, they cannot answer why they want to learn how to code, except for financial motivations. Because the question is often asked during job interviews, it is important to have a good answer. What can you do about it? In my professional experience, the royal road to the IT field is immersing yourself in a disciplined process of research, support, and planning.💡 This includes taking online courses (e.g. Coursera, Udemy, edX), finding a mentor (e.g. Women Go Tech, idialogue), and getting proper career coaching. An industry-informed coach will help you deal with your fears, collect your thoughts around your values, goals, and motivations, as well as come up with a reasonable career plan. After that, you will be able to provide solid reasons why you want to join the IT field as well as explain your vision and plan for the future. ☀️

Povilas GodliauskasFounder & Coach @
Mangirdas Adomaitis, I guess, the question was directed to me. :) I would recommend you looking at increases in popularity of online programming courses, programming bootcamps, tech mentoring programs, maybe tech YouTubers. However, this does not mean that there is no increase in popularity of computer science studies, but these are considerebly more popular among high school graduates.
View 1 more comment
For the Lithuanian audience! 🇱🇹 If you are interested to learn more about the mental health of the IT sector and mental health in general, you may enjoy this podcast. When Mindaugas, Head of Technology @ Vinted, wrote a LinkedIn post on his experience in therapy, I immediately knew that we should continue the conversation. So we did! And I am happy with the outcome. Of course, it was not easy to listen to oneself on audio, but nevertheless, it was a deep and insightful conversation. Spotify - Apple - Stitcher - Youtube -
S2E10 - Psichologinis saugumas. Povilas Godliauskas ir Mindaugas Mozūras - IT taburetė
⚠️ WARNING, a brain dump coming. Despite such great progress in personality theory and testing (e.g. big five, hexaco), it is unfortunate that we are still using dichotomous models (extrovert/introvert) to describe or, I would stay, classify people (including leaders) into categories. 🤦‍♂️ I guess, the reason behind the overuse of such classifications is their simplicity: you are either this or that, so why bother? However, just because the model is simple and easy to use, it does not mean that it is valid and reliable. Still not convinced? If so, you should look at more complex versions of the model (e.g. Jungian, MBTI) which essentially suggest that extroverted/introverted are not people's personalities themselves but rather their personality functions. Therefore, you get people who, let's say, are ENTJs. What is unique about them? Well, they have extroverted thinking (primary function), introverted intuition (2nd), extroverted sensing (3rd), and introverted feeling (4th). Example 1️⃣: think of orators or business leaders (e.g. Bill Gates, Steve Jobs) who usually come up with ideas while talking out loud, e.g. speaking to others (therefore, extroverted thinking), and rely a lot on their intuition based on creativity (therefore, introverted intuition). Or you get INTPs whose personality functions are ordered in the same sequence, but temperament is mirrored, i.e. thinking is introverted (1st), intuition is extroverted (2nd), etc. Example 2️⃣: think of engineers and scientists (e.g. Albert Einstein) who are also very insightful, but they prefer thinking in private (therefore, introverted thinking) and using intuition based on observation (therefore, extroverted intuition). If we go on, we will get at least 16 varieties of extroverts and introverts‼️ And to me, the model still does not do justice. Why? Because the model does not account for type variety. For instance, two people who are considered ENTJ can demonstrate different degrees of extroverted thinking, despite that it is their primary function. Therefore, models such as big five are much more scientific and valid, as they are tested against huge population samples and provide percentiles of traits rather than categories. Moral of if this thought dump: using only two types to classify people is fun, but too simplistic, unproductive, and, with all due respect to those who do not know better, super lazy, especially if we want to understand people rather than classify them.
Who is more effective as a leader, introvert, or extrovert? Organizational psychologist Adam Grant says his research shows that introverts and extroverts are equally effective as leaders, based on their companies' performance or teams. Whether introverts/extroverts were more or less effective depended on the kind of employees they had. Extroverts are better leaders with reactive followers, people who are looking for direction from above. If I am an extroverted leader, I will fire you up, get excited, and you will be ready to follow the direction I have created. Introverted leaders were more effective with proactive employees. If you have a whole team of people who bring their ideas and suggestions to the table, who are taking the initiative, extroverted leaders would feel threatened by that. They are like "don't steal my spotlight, I am in charge here". That has two negative effects: (i) they shut those people's ideas down, and (ii) they left their people demotivated. Introverts were much more likely to listen. And make people feel valued and get better ideas to the table. And we live in the world now where we need more proactivity from the employees. As the world is more dynamic and competitive, as a leader, you cannot see everything what is happening or going to happen. Given that proactive employees are more important than ever before, introvert leaders are going to be more effective in the future. Agree or disagree?

Mangirdas AdomaitisArtificial inteligence, Data science
Miglė Andrulionytė I am non-expert in human personalities. In general humans struggle to opperate well without structure. Oversimplified structure is better than no structure(if implemented sensibly). Like in a statistical saying: “all models are wrong, but some are usefull”? :)
View 10 more comments
As product development continues to shift more and more towards business-centered rather than human-centered design, removing “friction” becomes one of the key aspects of product optimization. Reducing “friction” pretty much means minimizing the cognitive load and number of steps a user has to take to reach the goal. However when you look at that goal from a business perspective it’s usually a conversion (most often some sort of transaction) and to get their users to that goal as quick as possible businesses are inclined to remove all friction blindly. The problem with that is that not all friction is bad for the user. Let me quote AirBnb’s design manager Steve Selzer - “...when we remove friction, we also remove moments for serendipity and self-reflection. At scale, this can erode our social values and increase our tendency toward intolerance and impatience, leaving us with a lack of resilience and an inability to navigate change.” Also one of the best examples of increasing instead of reducing friction comes from the same AirBnb - one of the last steps before you book a place is to send a personal message to the owner of that place. From a business perspective it’s absolutely not necessary and creates friction in the most important user flow of the product. But would they have decided to remove it or put it somewhere else they wouldn’t have built such a trusting community and wouldn’t have such a successful product. So be thoughtful with reducing friction and keep in mind that if used correctly and with the right intent it can actually benefit both your users and your business.
The Fiction of No Friction

Justas JanauskasCEO @ Qoorio
Agree with you and this is something on Ronaldas Buožis future list
View 2 more comments
Accesibility can still sometimes become an undervalued and downprioritised part of product development, unfortunately. What role does accesibility play in your product? And what challanges have you faced with it?
Supreme Court hands victory to blind man who sued Domino's over site accessibility
“Become smarter in 15 minutes a day”, “Learn a new language in a week” or “Get fit in 14 days” - some of the value propositions of today’s apps. In product design & development we strive to build experiences that are easy to use and simple to understand, and that’s great! But is there a danger in oversimplifying? What kind of lasting effect can simplified, “everything’s under the hood” type of experiences have? A designer & writer Ralph Ammer explores these questions in his nicely illustrated piece bellow
Make me think!
Talk about a bucket list branding project! Get your logo on a rocket, get your logo into space, and get your logo to Mars.
NASA Mars 2020 Mission — Logo & Identity
The so famed Spotify agile model with autonomous teams (well, guilds actually because teams doesn’t sound that cool) was never fully a reality at Spotify itself and yet is being copied by so many companies. While there’s a lot of issues with that model, the one that I’ve experienced the most while working with it it’s the assumption that everyone are good at collaboration. Well, they aren’t, it’s a skill like any other and it’s not a given. And while I still think autonomous product teams are a good idea, I also think that for it not to fail you have to understand that collaboration won’t happen automatically, it has to be a careful and methodical effort to practice and master collaboration product wide.
Spotify’s Failed #SquadGoals

Dominykas RimšaProduct & UX Designer
Antanas in my experience it mostly boils down to having the right leadership in management, tech and design as well as being able to set up your KPIs in such a way where both product wide and individual teams KPIs can easily feed into one another. You need good management to foster cross-team collaboration culture and good leadership to set KPIs that work well together.
View 1 more comment
When was the last time you used a Floppy Disk to save something? Do you even know what that is? Or how long ago was the last time you used an actual handset to call someone? These things are way in the past and there’s a whole new generation of people who might not even know what these are. And yet we don’t think twice when clicking on a Floppy Disk icon to save a document or a Handset icon to pick up a call on our touchscreen phones. Should we get rid of old people icons? Or are they good to stay? What do you think?
The Floppy Disk means Save, and 14 other old people Icons that don't make sense anymore - Scott Hanselman

Rūta SimanaitytėMaster’s degree 👩🏻‍🔬| Working in 👩🏻‍💻| Ultimate 🐕 ❤️
More importantly what would you use instead of a handset icon? 😅 Most of the icons have a story behind. I think this way it’s even more meaningful! You might not ever hold a handset but you know for sure that 📞 stands for picking up your phone ☎️
View 2 more comments
Lim Yien Yong on Personal growth and developmentLife enthusiast with an autotelic personality2 months ago
Have you heard of the First Principles Thinking? According to Elon Musk, he used the first principles thinking to design a cheap rocket from scratch, and re-use it by landing it back on earth, and with the same principles he revolutionized the electric car industry. Aristotle defined a first principles thinking as “the first basis from which a thing is known.” Here is how you can use this 3 simple steps of First Principles Thinking. ✅ Step 1: Identify and define your current assumption. Understand where you are standing currently should be the starting point. If you need to solve a problem, you need to think about the problem. This way you can have your problem defined and boundary set up. ✅ Step 2: Breakdown the problem into its fundamental principles. Fundamental principles means getting down to the rootcause of a thing, like back to the most basic elements of anything. The best way to uncover things to its basic is to ask question. You may wanna use the '5 Whys' approach, and if '5 Whys' is not enough to get you to the fundamental principles, add more 'whys'. ✅ Step 3: Build new solutions from scratch Once you have identified your problems and have broken them down into their basic truth, then you can begin to imagine new insights and turn them into solutions. Read more about this at:
First Principles: Elon Musk on the Power of Thinking for Yourself
Google has released a new set of best practices to rank high not just based on keywords or content quality but also on measurable UX of the website. Here’re some of the highlights: Speed - a webpage should load fully in less then 2.5 seconds Responsiveness - users should be able to interact with a website within 100 microseconds Consistency - layouts should stay as consistent as possible navigating from page to page Of course there’s so much more to great UX but it’s a great first step toward a more user-friendly web.
Introducing Web Vitals: essential metrics for a healthy site
Lim Yien Yong on Personal growth and developmentLife enthusiast with an autotelic personality2 months ago
Here is an interesting article I read recently which I want to share with you all. Learning about the differences between your "Thinking Mind" and "Observing Mind" can help you to negate negative thoughts and emotions during this very times.
Your Two Minds
Design systems are not easy but becomes necessary as the product scales. And as product grows the design system has to scale with it. Take a look at how Spotify evolved theirs, going from one centralized system to a framework that holds multiple systems under one roof.
Reimagining Design Systems at Spotify
Here’s a fun little game to test your eye for detail. Find differences between presented UIs and try to guess which one is correct. Easy at first but gets harder as you go. Share your scores!
Can't Unsee

Justas JanauskasCEO @ Qoorio
Good one!
Download Qoorio to comment, talk & learn
Become Open HumanFAQBlog