Proud to announce that Arianit Fazliu – Co-Founder of Kutia was a speaker at the Pirate Summit held on 6 and 7^th September 2022 in Cologne, Germany. 

His presentation Love, Mercy, Facts – A Human Approach to Leadership is a result of a deep analysis that utilizes Arianit’s personal experiences, different methods, learning, examples, and practices in conceptualizing this approach that aims to help leaders and other participants advance their organizational goals and ultimately promote the sustainability and success of any business.  

This session presented a new “back to human” approach in an organizational setting, as the only response to change in technological development’s constant state of flux. As leaders develop their organization’s human potential, this session provided them with an approach that will advance their organizational goals and ultimately promote the sustainability and success of any business. 

The session included experience sharing, examples, and practices on how to utilize the pyramid of Love, Mercy, Facts and let it become integral to the brand – and its reputation, by being spread throughout the organization – suppliers, partners, customers, employees, families, and communities.   

Believe it or not, humans couldn’t afford to live without feedback. The need for assurance in everything that we do goes back in time. From our childhood age, we needed affirmation in every step we took and every new thing we learned. We even acquired our language through reinforcement and imitation. Just try and make an angry face at a baby and you will see how he/she won’t smile at you. A second after, make a smiley face and see his/her face change immediately. Make a specific action when a child says a word and you will see how that will be inculcated in their head. It is the power of a reinforcement need that makes a major impact on how we can create relations with others.  

We need feedback in order to grow as humans and professionals. Feedback has the power to strengthen trust and respect between people, hence contributing directly to our psychological needs of love & belonging, and esteem. 

Getting feedback on both a personal and professional level is critical to an individual’s development and advancement. However, if the feedback is done incorrectly, it may sound like criticism. There is a feeling about criticism that can be perceived negatively by most people. In working environments criticism sounds like one-way thoughts after something has happened. Feedback, on the other hand, opens a door for a deeper understanding of the problem and leaves space for improvement and growth.  

How does feedback differ from criticism? 

Focus 

Feedback is frequently used to convey observations regarding how the work was completed. The receiver is made aware of the expectations for their task. This could contain suggestions for how to enhance future performance. 

Criticism is frequently aimed toward the individual who completed the work. If the work produces a beneficial result, the person is praised. If the outcome is less than ideal, it is common to assign blame. Since the focus of criticism is not on the issues that caused the non-completion of work, it is hard to leave room for improvement. 

Objectivity 

Feedback is both impartial and sincere. It evaluates the result of an action. If the outcome is negative, possible causes are investigated without assigning blame to individuals. The unspoken emphasis is that the individual must examine and resolve the situation. 

Criticism is personal. A boss is likely to share personal views on the cause of the bad result and insist that the team member take corrective action. Even if the manager’s judgment is correct, criticism has the effect of making the person hearing it defensive and irritable. 

Purpose Specification 

Feedback is defined by its clarity of intent. The project’s goal, the person’s role in achieving it, and how one’s actions will affect the team and the outcome should all be expressed clearly. 

Attitude 

Feedback is given with the intention of assisting in the resolution of an issue. As a result, collaboration and goodwill may improve. 

Criticism can appear to be judgmental. As a result of being inspected, the recipient may grow uneasy. Self-consciousness and a desire to disconnect from the topic and the person who is criticizing you may be prompted. 

Outcome 

Feedback allows for discussion and the exchange of ideas. A deeper examination of the problem may lead to a team member’s self-evaluation and self-correction. 

Criticism can lead to defensiveness, which can lead to missed opportunities for learning and self-correction. Emotions may become more intense. Arguments and a breakdown of trust between the criticizer and the critic are possible outcomes. Relationships, both personal and professional, are likely to suffer. 

Constructive feedback examples 

Instead of: “I think you could improve your public speaking.” 

Try this: “Well done for speaking in front of everyone, I know it can be daunting. For next time, try to look up a little more instead of looking down at your script. I have a book you can read to help you feel more confident to do this.” 

Instead of: “Your work isn’t written in line with our company voice.” 

Try this: “I really like how you’ve approached this piece of work. I have identified a couple of instances where your writing doesn’t match the company voice, so please can you revisit these again.” 

Instead of: “Can you make your work a bit clearer and consistent?” 

Try this: “Your spreadsheet is very useful and evaluative. However, the last two columns are not as clear as the rest of your columns. Please can you make them consistent with the rest?” 

Instead of: “I’ll discuss this piece of work with you in your next monthly one-to-one.” 

Try this: “I’d like to discuss this piece of work with you. Please can you let me know a time in the next few days when you’re free to discuss it?” 

Instead of: “I’ll email you feedback on your task.” 

Try this: “I’d like to give you some feedback on your completed task. Please can you let me know a time in the next few days when you’re free to discuss it?” 

Note: Feedback is extremely beneficial, so embrace both positive and negative feedback to create a more successful work environment. 

Today, the number of smartphone users worldwide is over 3 billion, and this number is forecasted to grow by several hundred million over the next few years. 

Apps are getting more ingrained in our daily and professional lives. They can do plenty of things; from executing financial transactions to uploading sensitive health data.  

At Kutia, we work with start-ups and established industry leaders, designing mobile applications that make life easier for their customers. One of the most important factors we look at when building mobile apps is security – how we can protect both consumer and corporate data, while still building an application that is meaningful for both parties.  

What are the security risks for mobile applications?

Threat #1 Malware 

One possible threat to mobile app security is malware, which is installed on the device. Mobile devices are often configured to only allow application installation from an authorized app store (e.g., Google Play or Apple Store). With malware, a hacker places a malicious application in an authorized app store, enabling the application to be installed onto targeted devices. 

Threat #2: Lost or stolen device 

Another huge threat is that mobile devices could be lost, or even stolen. A person with physical access to a mobile device may try to bypass the device’s lock screen in order to access sensitive information stored on the device. 

Threat #3: Code guessing 

A more straight-forward approach to bypassing phone security is the Code Guessing method. In this method, the potential thief tries to crack the lock screen passcode (typically a PIN or password). This could be by brute force or by something known as “shoulder surfing”, where someone observes the device owner’s use of the lock screen passcode.  

How to create a secure mobile app?

1. Source Code Encryption 

As most of the code in a native mobile app are on the client side, mobile malware can easily track the bugs and vulnerabilities within the source code and design. Developers should ensure that their applications are robust enough to prevent any tampering and reverse engineering attacks. Encrypting the source code can be an ideal way to defend your application from these attacks as it ensures unreadable. 

2. Secure the Data-in-transit 

The sensitive information that is transmitted from the client to server needs to be protected against privacy leaks and data theft. It is highly recommended to use either an SSL or VPN tunnel, which ensures that user data is protected with strict security measures. 

3. Make Provisions for Data Security 

When it comes to accessing confidential data, the mobile apps are designed in a way that the unstructured data is stored in the local file system and/or database within the device storage. However, the data in the sandbox are not effectively encrypted; hence, there is a major loophole for potential vulnerabilities. 

4. High-level Authentication 

Developers should design the apps in such a way that it only accepts strong alphanumeric passwords. On top of that, it is better to make it mandatory for the users to change their passwords periodically. For extremely sensitive apps, you can strengthen the security with biometric authentication using fingerprints or retina scan. 

5. Secure the Backend 

It is essential to have security measures in place to safeguard against malicious attacks at backend servers. Most of the developers assume that only the app that has been programmed to access APIs can access it. However, you should verify all your APIs in accordance with the mobile platform you aim to code for because API authentication and transport mechanisms can deviate from one platform to another. 

6. Minimize Storage of Sensitive Data 

To protect sensitive data from the users, developers prefer to store the data in the device local memory. However, it is best practice to avoid storing sensitive data as it might increase the security risk. If you have no other option other than storing the data, better use encrypted data containers or key chain. Additionally, make sure to minimize the log by adding the auto-delete feature, which automatically deletes data after a certain time. 

Our App Development Process  

To build a safe mobile app, first, we need to have a development process that fits the needs of each project. Success within the competitive landscape of these growth projections can become a reality for your company—but only if supported by a precisely cultivated mobile app development process. 

An effective app development process flow lays over seven key phases. Regardless of the size and scope of your project, we have developed a process that will make your enterprise mobile app development initiative a success. 

If you’ve already made up your mind and you’re willing to build your safe app, contact us at sales@kutia.net.