ChatCPT is fun, but did you try GitHub Copilot for iOS App development?
You can save a lot of time even if Xcode does not support it natively, but you can fix it. Here is how š§µ #ship30for30
Easy way - use VSCode with the Copilot plugin. I'm using VSCode when working on longer functions and business logic to have quick suggestions from Copilot. To compile projects or see previews, I just hit CMD+S in VSCode and switch back to Xcode.
It is possible to launch the iPhone simulator from VSCode, but I found switching back to Xcode comfortable and fast. Xcode feels handier to catch errors and debug code. If changes are made in Xcode, the VSCode editor updates them automatically.
A bit harder to configure, but an excellent way to use Copilot in Xcode without switching between IDE: CopilotForXcode project github.com/intitni/Copiloā¦
The installation process was smooth. We spent a bit more than an hour on one of the live streams. The hardest part was to find still available in Xcode shortcuts to set Copilot actions, but I finally got it working with help from the chat.
The third option is to use AppCode IDE for development, but after the announcement that this product is sunsetted, I can't recommend investing time and money into that anymore.
I'm using both - VSCode and CopilotForXcode. VSCode is handy when working on business logic and planning to create a bunch of functions. Rapid auto-complete is very helpful and speeds up development.
Xcode plugin helps when I'm working on UI, and I prefer to see previews and can wait a bit for every Copilot help request if I need any. It works but is much slower compared with VSCode.
Why should you give it a try to Copilot: 1) It can speed up your work quite a bit. 2) It is great to see suggestions from a virtual co-worker. You can learn something new.
Give it a try, especially if you are working alone and don't have a chance to review other developers' code.
ā ļø Do not forget to review Copilot's code. I saw quite a few dumb logic mistakes in the suggestions. Copilot has no idea about business requirements and, for sure, sooner or later, will generate errors even if the code is compilable.
ā¢ ā¢ ā¢
Missing some Tweet in this thread? You can try to
force a refresh
As a developer, you are getting all the money asap. As a customer, you pay once and use the app forever. The only problem is - it is not clear how long this "forever' will last.
Year or three, or a lifetime while the developer is alive.
Pricing for one-time purchases should be relatively high.
IMO, those should be 3+ years of App support and updates. That's quite a big responsibility to commit to working on the just-launched app for 3+ years.
So, the obvious choice for Habit App is a subscription model.
I love building iOS apps. I do that as a consultant and have a few indie apps in the AppStore.
Unfortunately, when I first got interested in iOS development, I had difficulty figuring out where to start.
It seems that finding learning materials still is a problem. So, if you also trying to learn more about iOS Development, here's the best way to get started:
ā¢ Go to This website: hackingwithswift.com by @twostraws will give you all the information you need to start. 100 Days of SwithUI is a free course, and you will learn all you need to build the first App.