Devoloping and running a simulator for iOS is so smooth experience I am in love with it. Though I am an android user developing for android is such a pain sometime. Android studio needs more improvement.

YEARS of practice. I had my ups and downs. I learned myself, left it myself early on, came back to it half a year later, continued since. Figured out that web development is not the hell I wanted and quickly fell in love with iOS development in Swift. Been riding on the wind ever since, learning something new every single day.

Today I made something that some time ago took me about 3 weeks in less than an hour. If that’s not an improvement, I don’t know what that is.

Practice makes perfect, don’t forget that. Although it sounds ridiculously cheesy and shit, this is how it goes.

I’m getting drafted tomorrow. Well, this is not exactly a full on draft and joining the IDF (Israeli Defense Force) right NAO, it’s what we call a rough draft: I am having a psychotechnical examination so the military can understand how much I need to go to a cybersecurity unit instead of going to Gaza LMAO.

How do you prove yourself?

I'm an iOS developer and I've been developing apps for a year or two now and I don't see anything hard in it I just think it's knowing how to wire things up and avoid common bugs I've also worked on a couple of complex apps and the idea is just the same.

I want to know if I really want to prove myself well (to myself) how can I do that and how can I challenge myself more to improve.

Ps: I'm by no way an expert and I know I've got a big road ahead of me but I just want advise to improve more in the right direction

You can talk for a lifetime of improvement, but what can you do when your boss sits near you and dictates his changes to the app you're working on?

Don't forget, this changes are on the opposite place of good common sense, interface guidelines (iOS and material) and TASTE.

First. I clarify my work schedule is from 7am to 4pm. I have a personal emergency so I must leave on time today.
Now my story: Today (finally) at noon they decide to publish the iOS and Android applications. The thing with the Android application is the other Developer is with a last minute improvement (since Monday) and is not over.

It's 2:45, the iOS app has already been sent for review, but Android is not. So when the Architect says that he already talked to the client and told him that everything is ready today, I asked the Developer if Android is already? and his response was "Almost I will finist at 3pm or 3:30".
(Hmmm) I'm worried about time so I say Ok, then Android will be published tomorrow! God he needs to finish the development, and I'm going to take new screenshot, do the merge with the development branch and everything that's need for a production release. So, the Project Manager says "Hell no! It will release today!" My answer: I have to leave at 4 and there is a lot of haste to do something so delicate.

I'm still waiting for an answer in slack from her.

Then the architect very "professionally" tells the other Developer to do it himself. It's almost 6pm and they still have not done anything

For Apple hardware, including iPhone, iPad, and iPod Touch, iOS app development is the most common way of making mobile applications . The software is written in the Swift programming language or Objective-C and then submitted to the App Store for users to download.

In case you're a mobile application developer, you might have had second thoughts about iOS improvement. Every designer needs a Mac PC— Macs are more costly than their Windows-based partners. Moreover, when you complete your application, it faces a tough quality survey measure before it gets circulated through the App Store.