In a day? I normally give them a week considering they only need to get familiar with our particular setup not X as a technology. Provide documentation and tell them to ask questions if they need to. After a week or so give them a small task and see how they are doing.

What???? Seriously I didn’t get one little bit of what you said

@Plasticnova that as well

Is he still on probation?

Here is an example :)

@hitko true in such cases you can use Kafka that sends messages to HA clusters that then can pass it on further to client side. There is always ways to implement this on BE.

@hitko that is very true for this example. In such cases you can use web sockets and have the BE push changes and notify subscribers. This way you get what you need only and can append new messages to your list. This again comes to proper BE design and picking the correct tools where needed. FE should only consume and display data coming from BE without modifying it or you’re risking to present incorrect data to your users.

@hitko this could also be achieved with proper backend architecture and designed in a way that it only returns the data you need. Trying to fix backend issues on front end always leads to inconsistency and unexpected behaviour. I don’t think the example you gave is actually FE problem. Source of truth should always come from BE since your business logic will run there. Trying to manipulate the data on FE could be a risky since many factors can contribute to errors like database write issues or loss of network just to name a few. Last but not least you can’t control or fully trust user device which is not true for your backend.

@bartmr I can see your point as a web developer. However all of those are easily achieved in native code apart from the time travel Redux like state management for which you would need to use a framework. In fact I don’t see all of the points you mentioned as limitations at all. Multi threading is a lot more flexible and advanced written in native code as you have more control on what gets dispatched where and you can pause, cancel and remove tasks from the queue etc. Making a HTTP request really takes 3 lines of code max for most parts. If you need a time travel state management then your screen might be way too complicated and should be separated out logically. However if there is a reason that you really need that state management you can do it natively as well as I mentioned above. Last I don’t see how this would be easier to test. You have no control on how your js translates into native code never mind testing it. You can only test your js or am I missing something?

This is the reason its called estimate :)

Out of curiosity what are those native limitations?

That is interesting because from all I’ve seen so far from this “native” apps they’re rarely tested properly and have loads of crashes in the memory heap that always lead to a dead end stack traces. I’m happy it worked well for you.

@bartmr do you write any unit or UI tests for your apps?

@TitanLannister I agree with you. In reality if you want to run some code on a client side you would need to use javascript regardless you like it or not because this is what the browser supports. Why not follow the same logic when building mobile apps?

I can feel your pain coming from strict typed language like Java into something very loose like Javascript and having to wrap your head around it could be time consuming and painful. At the end of the day this is the path you need to take to achieve almost anything that requires dynamic content nowadays. I used Javascript in the past, didn’t like it and I try to steer clear from it for as long as I can. Again personal opinion but that’s why there is other people who like it and are really good in it. Just not my cup of tea

There is also a thing called “fast follower” where you leave the heavy lifting on the pioneers, learn from their mistakes and successes and make the product better. This way it will cost you less to triage markets and improve the product based on demand and user needs.

@Salim use to work for a company where the CEO was saying to me that he has a friend who runs a similar company and he only pays one developer to write “hybrid” apps. I told him wait 6 months and ask him again how is the app doing. Guess what happens next. App was very unstable and had loads of crashes that were hard to reproduce. It also went to a stage were they needed something more custom that required some specific native code to run that wasn’t possible using what they were using so had to write some spaghetti code that worked half the time. That same CEO had to pay an external agency to re-write the entire app from scratch costing a lot more at the end. I am sure there is more examples out there. To this day I am still looking for a valid reason not to use native code when building mobile apps.

Problem comes from web developers trying to write mobile apps. People are too used to whatever language they use on a day to day basis (hint javascript). Cordova like webview based frameworks are shit - full stop. Other frameworks that port to native code are a “bit” better but from experience I can tell you that whatever way they all work it maxes out the RAM and the device pretty fast with extensive use of the app. On top of that the binary becomes 10x bigger and requires WiFi to download.

If you only need a simple mobile app the you can justify the use of “hybrid” app, but anything more complicated than showing more than 3 screens that involves some business login, and requires back compatibility I’d go native.

My personal conclusion is always use native language for mobile apps you’ll thank me later.

@netikras I am assuming by saying “On a domain available to the general public” he means that none of the security measures you mentioned were present. Again only guessing here.

Hope this devs are not in a 3rd world country because your lawsuit might not go as smooth. However saving some bucks doesn’t justify the risk of incompetent developers. You get what you pay for.

Had to create an account with a local carrier and was forced to use up to 7 chars long password which is restricted to alphanumerical only input with at least one uppercase and one number. I guess I was left with very few options. No idea who makes all this nonsense restrictions based on some database “performance” requirements.

I’d go with what it should be instead of showing off skills. This days a lot of people over complicate code for this very reason and I mean I’ve seen this a lot. Just my 2 cents to your question

@M1sf3t do you remember Bill Gates presenting his new Windows and the screen went blue back in the days

@torbuntu you’re a bit harsh. Everyone is entitled to choose whatever they find fit. Classic “I hate Apple but never got to use one” case in my opinion. What is your personal preference? Microsoft or maybe Google products? I bet you have a wet dreams about Andoid too

Try restarting your computer. Sometimes appstore app is not able to determine its real free space

Yeah you would use push —force but make sure you don’t pull before as might be suggesting by git

You can use direct debits. The upper limit of a DD is about a 1M USD as war as I remember. You would be required to submit some extra paper work with your bank in order to be assigned a merchant id etc. This vary based on your location, local laws etc but you will be able to create invoices and direct debit mandates for a variable or fixed amounts and still be able to use Stripe’s API just the payment method will be different

Awwww not even close

Always use SSL/TLS aka https with ssl pinning to block newbies intercepting your requests. In addition to that use your API key with time based challenges to re-authenticate and adjust your sessions duration accordingly. All of this increases the security but remember nothing is unbreakable. If someone is determined they will make they’re way through. First you need to asses the risk, define security measures to protect yourself/your users from theft or impersonation etc. Do not over engineer your API is my last advice. And last you can store the key in the device keystore never in the shared preferences. Once you have timebased challenge in addition to using your key it will make reauthenticating with same hash very hard.

@simonblack I don’t know to be honest. I have worked in a small startups and large corporations and in all places this was the case. For example our current CTO has won an award in AI and ML and comes from another very large organisation where he was leading a very big team for innovations.

My two cents: I wouldn’t want to work for someone who is going to tell me how things should work without any technical knowledge.

CTO stands for Chief Technical Officer. This title is given to someone who should mentor, design and drive the technologies used by the company. I don’t see how this is going to be possible without broad knowledge of systems, programming, databases, security etc. the list goes on. In all companies that I have worked in the CTO is the most knowledgeable person that can give guidance and explanation behind every decision made. That being said it makes sense for this person to be paid a lot more as their knowledge and experience is massive and very valuable