Xojo is a fantastic prototyping tool to build concepts or simple apps.
xCode with SwiftUI is still too complicated to be used by designers.
There are tools coming like judo.app but only for iOS.
Will be great to see Xojo offering the export or conversion to Swift and SwiftUI for Xojo developers.
Swift 5.8 seems now mature.
I’ve been playing with SwiftUI over the last few weeks and what I’ll tell you is that the coordinate-based system that Xojo uses is just not compatible with the structure of SwiftUI.
FWIW, I happen to be a visual programmer and I find no issue with doing layouts in SwiftUI, you just need to take the time to wrap your head around it. Additionally, taking the time to do so will serve you well because almost all of swift uses the same motifs, and it becomes very natural after a time.
4 Likes
swift as language is great but apple programming framework and concept “swift ui” is worse.
much devs using a bad notation (writing style) by adding all together by dots instead of calling methods.
you can not convert xojo into swift ui because different frameworks.
putting a ui together in swift ui is easy if you have a base project for your needs.
xcode have a preview method, if you change code the ui get updated.
putting things into a VStack, HStack, ZStack is simple.
most issues are the struct and oop which not do what you will expect.
as example if you change an object it can update the ui.
if user change the ui it update the object.
if user close the app the data get serialise into a document object (concept) and saved.
(i mean fully automatic!)
swift playground is nice but can not use straightforward in normal projects.
forerunner of SwiftUI was UIKit, if you look for code snippets u must know
in what project type it was made.
The majority of developers I know loves SwiftUI. Infact, I started using Swift and XCode just because of SwiftUI. It is such a powerful and natural way to build user interfaces.
@OP
I suspect that you’ll ever be able to export something Xojo to another platform, since they are all competitors and Xojo tries to keep you save and sound within its own walls (what I find completely relatable).
So either you deal with the clunky Xojo Mobile Platform or you do things in Xcode. Both together won’t happen I suppose.
3 Likes
I’ve just signed on and trying out a months subscription to JUDO on App Store - a graphical editor for crafting SwiftUI desgns that can be ported to Xcode and swift.
Will let. you guys know how I get on
2 Likes
What you said is… incorrect.
What you call “bad” is how most modern languages do (I don’t know for how long, more than 20 years?) since OOP and functional programming and is much more readable than the pre OOP languages era used to. You are used to old ways and just need more practice. Method chaining, like
var scrambledEggs = getEggs(2).addSalt().addSpice().mix().fry() // clear readable natural sequence
is much more natural and readable than
var scrambledEggs = fry(mix(addSpice(addSalt(getEggs(2))))) // reading mess
5 Likes
@Rick_Araujo what i wrote about swift ui is exactly.
its not about the language, its about how it is used by developers.
please use swift ui for a month or look at least at source code/project examples from others.
theoretical yes but you underrated other prople creativity with all possibilities.
seeing a nice row like this is rare in swift ui. its usually across hundrets of lines …
var scrambledEggs = getEggs(2).addSalt().addSpice().mix().fry() // clear readable natural sequence
for fun i build a Kanban Board from scratch with FileDocument concept in swift ui. (with neat source code of course.). every change in ui input is saved automatically with apples concept.
you can do this too and afterwards judge this apple xcode swift ui again. 
1 Like
We use FlutterFlow to prototype our iOS / Android apps. Fantastic tool!
1 Like
Don’t start this way, take a course on the subject, you can’t learn just by looking at third-party code without understanding what’s going on.
Fundamentals takes like 12h. Do a search on YouTube.
i had read a swift book, the apple framework documentation, visited a main stream forum, also youtube videos.
swift playground. …
frequently surficial explained and what i needed for my project not there or not the way i want.
i collect much knowledge but the ide and framework nag for all you are doing in combination.
videos and documentation get very fast obsolete and stay present for what ever reason.
if you think a map system with routing can be solved in swift ui, no its half baked, many features are missing there which ui kit had (obsolete kind of projects still used for a reason).
the most time is used to find why something not work as expected.
if people working for years in xcode they are familiar with all kind of issues.
maybe is xcode not bad and ms vs ide with c# just more familiar for me.
ok