Posted on

What app to build in 2017? Native, Hybrid or Progressive Web Apps?

The global apps debate got another dimension as Google proposed progressive web apps as the next big thing in 2015.

However, most people building apps today still prefer native apps, for several reasons, mostly because it’s what people actually use.

We gathered three experienced developers and CTO’s to discuss the three types of apps most developers are building today. jordimirobruix, former CTO of Wuaki.tv, senior developer at Ulabox, Rubén Sospedra and founder of Javascript coder bootcamp Codeworks Alessandro Zanardi.

Friction, friction friction

A big question in the app-building discussion, is about the app install friction. In other words how many clicks there are from finding the app in the app store – to becoming an active user.

After voting on what type of app most people with build something with tomorrow, more than 40 percent of the people attending the debate chose native.

Briux believes the friction is the same in both PWA’s and native apps:

What’s the difference of the friction generated by the app store, compared with downloading a web app to your home screen?

Zanardi believes progressive web apps is much more frictionless because the device itself promotes the use of PWA’s:

There is much less friction in installing a progressive web app because the device your using is actually wanting you to install it. Compared to going to the app store, installing an app that takes up tons of space, and needs an update every two weeks.

Sospedra turns to the metrics:

The numbers tell us a story when 86 percent of the media being consumed on mobile phones are through native apps and only 10 percent of the total time spent on smartphones are used in browsers. PWA’s are still the new kid on the block, so maybe in five years we can talk again?

https://upscri.be/285782-2

The evil app store?

In one of the last question rounds, the app defenders had to reveal their answer about app stores — good or evil?

Miro says that if you get rejected it’s an evil thing and continues:

Android is pretty easy, just push and you’re in. With iOS however, to wait for someone from the other side of the world to test your app, that’s a black box for developers and nobody likes black boxes.

Codeworks CEO Zanardi points to that the app store or Apple, is the biggest preventer for making PWA’s really big:

The biggest problem PWA’s have at the moment is that Apple’s Safari doesn’t support service workers and that kills a lot of the purpose of the app. Firefox and Chrome are embracing PWA’s. As long as Apple is making tons of money from the app store we’ll have a real challenge.

What does your startup need?

Former Wuaki CTO Miro says choice of app to build all boils down to what kind of business you’re building:

If you asked me four months ago, hybrid apps were not the way because we couldn’t build what the business needed in Wuaki. But today for what I’m building, we’re looking for speed, something that’s tested and reliable and we wanted access to Canvas or WebGL, so hybrid is the way for us today.

Miro explains how the business decisions often dictates what kind of apps you end up building.

Sospedra agrees with Miro, saying that your business goals need to be clear before deciding what kind of app you’re building. He’s also adding that what kind of technology your team is comfortable with is important as well:

If you have a team that are really good at Javascript, then go for React native, but that’s my opinion.

As progressive web apps might be the bet for the future, Zanardi wanted to end the discussion with a statement:

I completely agree with these guys that if you’re building an app today to work on iOS and Android I would go native. The main problem you would have with PWA’s is with the iOS. If you’re targeting mostly Android devices you might go for a PWA. As long as Apple is blocking the spreading of PWA’s we’ll have an issue we need to solve.

There was a lot of other interesting points in the full debate, so check out the video at the top!

The post and video was produced by the itnig media team Masumi Mutsuda and Sindre Hopland.

Posted on

Undressing a CTO and how to become one

Do you want to become a Chief Technology Officer, or are you just curious about the role?

If you want your keyboard to remain your closest friend, you can stop reading right here, being a CTO is much more than just being a talented developer. But if you want to get some insights from three experienced Barcelona-based CTOs, please continue reading.

Investing time in your team is the most important task, even more important than focusing on your product.

Right place at the right time

Roger Campos from Camaloon (to the left) says that personal experience is much more important than how many years you have worked in a company.

In the startup world not all decisions within the company are carefully planned and executed according to the planned strategy.

Pau Ramon Revilla, former CTO of Redbooth, and currently founder at Factorial felt he was at the right place at the right time when stepped up as CTO for the first time.

I started at Redbooth, living on the founders sofa in San Francisco, coding for a roof over my head, so I wasn’t a very expensive developer. But as I went back to Barcelona, the former CTO and the tech lead left, and I was asked to be the new CTO.

For others it’s more of a transitioning after starting a company from scratch.

Both Albert Bellonch at Quipu and Roger Campos at Camaloon founded their startups, and gradually grew into the CTO role as their companies grew. Roger never really set out to become head of tech at Camaloon:

It was never a goal of mine to become a CTO, but you take on responsibility and do your best to grow a great team.

The biggest challenge — new developers

A huge challenge for most CTOs these days is finding talented developers in a highly competitive job market.

CTO Pau Ramon Revilla and Roger Campos says personal motivation is key when hiring new developers.

But what kind of developers are most tech leaders looking for?

They all agree that the most important aspect when hiring, is personal motivation, and if the person is willing to go deep in all kinds of challenges he or she faces.

Experience is important, but having worked for many years, is not necessarily the only metric that is valued, say Roger:

If a developer has worked in five different jobs the last years, doing the exact same task, to me he is less experienced than a younger developer, that has worked on many personal projects and faced complex challenges.

Pau gives junior developers two tips:

The startup world may be too harsh for many junior developers. To get the right kind of experience I would advice to contribute a lot in open source, and maybe take a job in a big corporation the first years.

https://upscri.be/285782-2

Invest in people

People have different skills and methods on how to lead a technical team, but the three CTOs agree that people is the most important focus for them in their work. Pau explains:

Depending on the company, most of the time the development team will be the most valuable asset, sometimes even more than the product itself.

All the CTO’s agree, and Roger says:

My biggest task and most important mission is to talk with people. Talk with my team, with the rest of the company and external people, that’s most of my job.

I keep coding to keep my sanity

Albert Bellonch (to the left) is still coding every day at Quipu, but will soon have to stop to code on a daily basis because his team is growing a lot.

It’s no secret that time spent coding decreases a lot when you move over to the role of being a leader.

Albert is currently leading a 4–5 development team at Quipu. He’s happy he’s still able to code every day:

I still code on a daily basis, and I’ve been able to create some cool new features for Quipu, but as my team grows by the months, I will soon stop coding every day.

Soft skills

A developer that has the aspiration of becoming a CTO should have a lot of experience, but there’s also other skills that are vital, says Pau:

Focus on the soft skills, you need to be able to reach a consensus with people, not only focus on your own opinions.

All the CTOs agree that you don’t need to be the best developer in the company to lead the development team, but there are some skills that are good to know these days, according to Roger.

It’s hard to point to one kind of technology, because everything depends on what kind of project you’re working on, but Javascript is probably the safest bet for a developer today.

(If you want more insights, check out the video at the top!)

……..

This post was written by Sindre Hopland and the video was edited by Masumi Mutsuda — the itnig media team.

Posted on

Hacker Bootcamps VS. Universities: What to choose and what's in it for the future?

Hacker schools or bootcamps are getting more and more popular. You’ll learn a programming language in 2–3 months, and you’re more or less guarantied a full-time well paying job.

If you compare this to signing up to a four-year degree at a University and getting tons of study loan, the short-cut through a hacker school is obviously tempting.

But what are the incentives to attend university, and does a “degree” from a hacker school limit you in any way?

We asked the experts.

“If you want to work go to a hacker school, if you want to work at Google, go to University”

The big pro about hacker schools is obviously that the distance from the school to work is a lot shorter, but is a person well prepared to work in a startup after graduating from a 2–3 months program?

“You can not become a CTO with just a bootcamp experience!” (Marc Alier, UPC)

CEO and co-founder at Codeworks a Barcelona bootcamp, Alessandro Zanardi, acknowledge that universities are vital for training specialists in more complex computer science areas:

We need engineers that have stronger theoretical experience. If you’re dealing with big data or artificial intelligence you need developers that have a university degree. If you want to work at Google with AI, get a Ph.D.

The university problem

Marc Collado is director at Iron Hack Barcelona, a bootcamp that also have campuses in Miami and Madrid. Even though Collado now represents a bootcamp, he himself went through a five-year University program at IQS:

The universities are too embedded in society. At Iron Hack we analyze the job market, and work towards creating a program that actually helps businesses hire a much needed workforce, and gets people into jobs.

Ludo (Marc Alier) hopes universities change the way they treat their professors and teachers, and agrees with the bootcamp hackers that there is a lot to be improved with the institution stretching thousands of years back:

The problem with University is that the professors are incentivized to be researchers, not to be good teachers. You get promoted if you’re good researcher, not if you have experience from tech companies or do a great job as a teacher.

Bootcamps do not build CTO’s

Professor Alier is grateful that bootcamps fill a whole and a demand in the market, but he wants to make one thing very clear:

I have seen examples where people have finished bootcamps, and they’re told that they can start a company. I’ll tell you this, they always screw up, always!

He continues:

You can not become a CTO with just a bootcamp experience!

Zanardi at Codeworks does not like the negativity towards the concept of screwing up:

This is a classic example of the difference between bootcamp mentality and university mentality. The best people from all sectors and industries are people that know what it’s like to fail hard.

Also Iron Hack’s Collado weighs in on the CTO statement:

A CTO needs more soft skills than hard skills, it’s about experience, recruiting, mentoring, but yes of course the guy needs to be technical, that’s for sure.

……….

The post/video/podcast was produced by Sindre Hopland & Masumi Mutsuda, the itnig media team.

https://goo.gl/forms/gBIKRZP0fnqmaFda2