Too much code.

bartoszswiety Uncategorized

I have to admit to some trouble. Always wanted to just gain all dev skills to build my things, but it looks like sometimes too much experience might be a blocker for your creativity and new ideas. Maybe because we finally understood the real value of time? 

On the other hand, you can finally see the market from a more cold-head perspective than all these wannabe founders. Let’s face it, most of those cool startup ideas for the next “barber app”, have no real long-term value and can’t be easily scaled.

What I’m trying to do now, is just overcome my weak sides and expand my soft skills like communication and marketing. It gave me a fresh look at some business models and made me think differently about “ideas” with a new perspective. 

trust karma, do good things and good things will come your way 😉

Flutter is not as bad, if you still can code in Swift ;)

bartoszswiety Uncategorized

Oh dear, I can never forget those discussions about what is better, how should I make the app etc etc.

The answer is always the same: it depends.

but you don’t have to take that decision now.

The best in flutter is that you can easily make native UI’s without having to recode them to all platforms.

But as we know, iOS devs hate to code logic in the another layer. We love to feel close to hardware that’s why. You should try to use MVVM model where whole Model is stored Swift Layer.

In this solution Flutter could be used only what it did’s the best. Representing views, also it allows your team to have only one frontend for all platforms 😉

How to communicate with your Platform Manager.

bartoszswiety Uncategorized

Can’t never forget the first meeting with Manager, I was so stressed and wanted show up myself from the best side.

The problem is that I’m allways trying too much, instead of presenting my self and my skills I was more focused on dumb asking questions, which showed me in bad view. Of course it’s always good to ask questions, but never show your weakness and lack of confidence behind them.

How to ask questions which doesn’t sound so dumb.

Instead of:

Do you have any crashlogs in the App?

Say

What do you think about metrics in crashlog, do you think that those are satisfying for you?

See that questions shows your knowledge about the complex processes, with leaving a branch of new topics to consider together

The best is that if they don’t have crashlogs already, they would ask YOU why it’s worth to have them. The whole point in such meetings is to share some opinion.

Why you need to analyse your SDK.

bartoszswiety Uncategorized

Of course it’s obvious that your app needs some fancy Analytics via eq. Firebase, Amazon… But what about SDK’s?

This year I’m working a lot about Identify Proofing SDK for my client. Although we gain pretty nice success rate (94%) some clients still had complained about OnBoarding Process on mobile devices. Unfortunately it took us about 3 days to get not final conclusion like:

I would give a lot to get some metrics from our SDK to know what really is broken there.

Why we did not put Analitycs before into our SDK?

Why it’s so hard to gather metrics from already existing SDK on Mobile?

Better is done than over engineered. – Keep it simple, and start gathering data ASAP.