Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Peter (00:01):
What's up, everybody?
Welcome to the Compile Shift
Podcast. This is the firstepisode of 2025. I'm your host,
Peter, and Geoff is here with meas how are you doing, Geoff?
Geoff (00:10):
Hey. I'm here, and I'm
ready to get this New Year
started. How's it going, Peter?
Peter (00:14):
It's it's going okay. I
feel like in Texas here, you
know, I've I've had my snow andice. That's it for another year.
I had the 2 days. Man.
Geoff (00:23):
I I started I started my
year in rural Missouri, and we
definitely got our share of iceas well. So
Peter (00:29):
There you go. At least
you hey. You got away on a
vacation. Mia, I had astaycation. So basically,
because I just decided I'mstaying in.
That's how that went. Alright.So in this episode, we're gonna
we're gonna do something alittle different here. We're
gonna look ahead and we're notmaking predictions for Apple or
(00:49):
anything like that because, youknow, we know Apple will release
the fastest whatever it is thisyear and they'll be super
excited about how we're gonnause it and can't wait to charge
us for it or something alongthose lines. We are gonna be
talking about our plans for thisyear in the hope that maybe it
motivates all of you to thinkabout this and if you've not
thought about planning ahead foryour year, maybe this will give
(01:12):
you something to think about.
So we're gonna be touching onour own personal apps and and
that kind of thing. So we'regonna get this started here.
Stop bawpling, Peter. Go back tothe document. So, Geoff, you got
any plans this year to mayberetire old applications or do
you think that this kind ofthere's some things in your
archives that are like, okay,end of life now?
Geoff (01:33):
Yeah. I think I I need to
slim some things down a little
bit. I've got a couple apps thatI haven't worked on in quite a
while to the extent that Appleis even, like, sending me emails
and saying, hey, you're gonnakeep working on these or not?
And, I've I've actually, at thispoint, by the time people hear
this podcast, have alreadypulled them off of the App
Store. And this is my app,Scroll Notes, which was a simple
(01:56):
note taking app.
It had a single note, and allyou could do is add to or remove
from it, but had a lot of decentsystem integration back in its
day. Haven't really touched itin quite a while. It had some
fun syncing issues, and soreally kinda killed momentum to
work on it for a while. Andthere have been a couple decent
competitors that have come outsince then. I feel like that
(02:18):
market's handled, and there'snot really too much that I can
do to put my own spin on it.
Okay. And then additionally, Ihad an app that I had done a
while back for a local museumhere in Seattle, Washington, and
that app never really wentanywhere after its initial
launch. And we really weren'table to contribute too much to
(02:39):
it. And there had been some dataissues with that as well. And so
because not able to reallycontinue contributing to it,
I've also pulled that one off ofthe store.
Peter (02:50):
Alright. So for me, I do
have one that I'm I think I'm
gonna retire because it neverreally I couldn't do everything
I wanted because basically theAPI there were no APIs
available. So I have a an app,FX Preset Manager, which was the
first personal app I put in theApple Store and it allowed me to
(03:13):
store, the presets for Fujicameras, the X system. It's kind
of like a film simulation thingand you can only store a few on
the on the camera itself. Andso, you know, like like many
things it's like, well, I got abunch of presets.
So I wanted an app that wouldallow me to store those on the
(03:34):
move so that I could, you know,put them in the camera anytime I
wanted to and made thatavailable to other folks as well
and it's had downloads and usersand everything, but
unfortunately, Fuji stillthere's no way to, like,
directly upload it to the cameraor download it. There's just no
access for that, which I washoping maybe there would have
(03:55):
been one day, but doesn't looklike we're going that way. So
I've decided that I'm gonna keepusing that app personally, but
no plans to to upgrade it orupdate it or anything like that.
Haven't fully committed toeither pulling
Geoff (04:10):
it from the store because
it still works and it's still
completely usable, but therewill come
Peter (04:15):
a point where, like you
say, it's like, okay, Apple's
gonna say, hey, are you sureabout this? So, you know, I'm
sort of retiring that one, atleast as far as continued
development on those. Now whatabout is there any apps that
you've did that you've got therethat you're gonna sort of you
thought, oh, I you know, I'mgonna pivot and take it in a new
(04:37):
direction at all?
Geoff (04:38):
I don't think so. I think
I think my focus this year is on
some brand new ideas, but we'llget into that a little bit
later. But I think you havesomething that you're planning
on pivoting. Right?
Peter (04:49):
I do. So, you know, we we
spoke about this, you know, my
job finder tracker app got aupdate at the end of last year,
with the resume support, and asI was doing that, it's kind of
one of those, you know, how youwhen sometimes you're working on
an app and and over time yourealize the the greater
potential that you didn't sortof fully see for it at the time,
(05:11):
when you you started designingit from sort of day 1 and I'm
gonna pivot it. It's it's gonnaremain what it is, but I'm
pivoting in the sense of doing,you know, more than just
tracking job applications. I seevalue there in in looking at it
and going, you know what, thisreally should be job
applications and related, dataslash sort of functionality and
(05:37):
things like that, you know,things like, oh, you know, it
should have calendar integrationand those kind of things. Don't
want to commit to too manythings in it right now, so it's
it's a pivot in the sense ofexpanding its usefulness.
I'm I'm pretty interested indoing this. I think there's a
lot of value there now,especially now that I've updated
some of the code base as well.So so that's my pivot, for that
(06:00):
one there. So the next obviousquestion, you know, is there any
anything that you think is gonnabe like a brand new app that you
you wanna talk about?
Geoff (06:09):
I think I'm gonna have
quite a few this year. I I will
kinda get into this a little bitlater in terms of plans as a
whole, but I think one thingthat I want to try to do this
year is expand more into havinga lot of little apps and maybe
maybe taking that in a slightlydifferent direction, a slightly
(06:31):
different, you know, almost moreof a business pivot than an app
pivot. Mhmm. And really kindaputting out a lot of smaller
apps in a sense that, they takeless time to develop and can
kind of get more ideas out thereand really see if I can build an
app that hits in the market in away that none of my apps have
(06:55):
really done so far. I've spent alot of time on apps where I
spent a real long time on them,and I really want to polish the
heck out of them.
And I I wanna have, like, theperfect app before I ship it at
all. And that hasn't reallyworked for me in the past, and
really, I think what I need todo is get more ideas out there
(07:18):
and expand on them from there.And, you know, kind of got to
see this a little bit with thelast 2 years' big projects. So 2
years ago, my big project that Ispent forever and ever on was
the Kineo release for VisionPRO.And spent a very very long time
(07:39):
on that one.
Over half a year on that one.And, if you've been in the
Discord, you've seen that I'veI've been posting about my
single digits of users. Not notnot really worth shipped Bark in
(08:02):
30 days or something like that.I think I even started I wanna
say it was like 23 days orsomething. Yeah.
Ship to Bark in just a handfulof days, and that app did
significantly better. And so Ithink I want to try and do
things more like that. But Barkeven to an extent was itself a
(08:22):
bigger app, where I kind of didthis land and expand type
strategy where it's like, okay,yeah, I got that first app out
in 23 days. But then I continuedto, like, make Bark my main app.
And I think I wanna do a lotmore of, like, what can I do to
get an app out in 30 days andthen go on to the next app and
and do that in 30 days and go onto that?
And I'm not saying that I'm notgonna bug fix or I'm not gonna,
(08:43):
you know, continue to improvethings, but really more rather
than having one app that I spenda ton of time on and if it flops
then I've wasted all of thattime.
Peter (08:53):
I gotcha. And, you know,
I mean, that's that's a I I can
think of some developers, won'tname them, but developers out
there who do just that. Lots of
Dalton (09:02):
Yeah.
Geoff (09:02):
There's a lot of very
successful developers who do.
Peter (09:05):
Yeah. And I you know, it
it's almost wrong to call it a
small app. I would say dedicatedapp, right, to a particular task
or Yeah. Whatever that may be.
Geoff (09:16):
Small small app, not
necessarily the right term, but,
like, small development timeframe.
Peter (09:22):
Yeah. Yeah. Right. And
and I think the advantage to
that too is, yeah, it enablesyou to get more out there,
right, and and see see whatbites. Right?
And and then maybe somethingbecomes bigger later on or like
you say, it's like, oh, well,that didn't really work and and
we can let that go, you know.And and interestingly, late last
(09:42):
year when I was listening tosome game development podcasts
and that, they were saying thesame thing about game
development in 2025. It probablyshould really be about smaller
games for those same reasons youjust said. Right? Shorter
shorter development cycles, getthem out there, see how it goes,
you know, the the big monolithicgames, were not really working
(10:07):
towards the end of the yearregardless of how big the team
or company or whatever behindit.
So so there's that as well and,you know, for my part, I I have
2 things that I want to do thisyear. One of them is one that
continued to bite me over theholidays, which is, my
(10:29):
subscription tracker. Now, yeah,again, you know, I know there's
a lot of them out there butthere's not one that is what I
want it to be. Right? And thisis something that we've spoken
about before, you know, makingan app for yourself is the best
way to care about an app.
Right? At least in the earlystages and to get it done. So,
you know, I've got that that Iwanna do and then make that
(10:52):
available for folks as wellbecause I had a bunch of
subscriptions renewed that Ithought I'd cancelled, turns out
I didn't. So it's like, okay,remember that again for next
year. So, I want to get that appdone and I feel that's a pretty
easy target.
It That's a dedicated to aparticular thing and I don't
think it'll take that long. It'sit's pretty much another, CRUD
(11:17):
app. Right? You know, so that'sjust fill in a form, store it,
delete it, update it, whatever.Shouldn't take that long.
Make it look reasonable. Sothat's number 1. Something else
that I'm not gonna go into toomuch detail at the moment, but
we we hope to soon is a projectactually. It's not so much it's
(11:38):
an app, but it's more of anonline service that I'm I'm
helping and and being a big partof and, I'm basically
responsible for the engineeringand technology on this, which
is, a project called UpcoastLeaders. I'll put a link in the
show notes.
We're not talking about it toomuch yet because we are in the
(11:59):
process of putting it alltogether, but I'm I'm sort of
essentially the the technologyhead on that. And so that's
gonna take a lot of my time andI'm I'm pretty pumped about
working on that as well. I'mbound to talk about that more in
the future, so I'm gonna leavethat one there.
Geoff (12:18):
I I guess the next
question going forward is, is
there anything that we'relooking for in terms of
education and learning thisyear? Any any sort of new,
things that you were going on toabove and beyond the typical
iOS, macOS development thatwe've done so far. I know for
me, I really wanna get more intothe business and marketing sides
(12:40):
of my business and really kindof expanding that, beyond the
the amounts of development thatI'm going to do. But then also
in development, you know, Ithink I might be looking into if
I'm making a lot of thesesmaller apps, maybe I should be
making some of them on otherplatforms as well. So getting
into some maybe some Androiddevelopment and maybe even some
(13:03):
front end web development andjust being able to have some of
these things available, not juston iOS, but being able to expand
their reach no matter whatdevice they're using them on, no
matter where they're at, whatthey're trying to do at any
given point, really expand theseout so that there can be a wider
market for them.
Peter (13:21):
So you don't have to
commit to this, but I feel
compelled to ask the questionthen. Write once, cross
platform, or native platforms onboth?
Geoff (13:32):
That that's tricky. I I I
think I'm gonna have to do some
investigation of that myself.
Peter (13:37):
Okay. Alright.
Geoff (13:38):
Fine. I've definitely
done some work with cross
platform tools before. Iactually wrote a app over the
holiday, not public in any way,shape, or form, using skip
tools, which I know you've hadthem on this podcast before.
Yep. Wrote it.
Wrote it. Wrote it.
Peter (13:54):
Wrote it. Wrote it.
Geoff (13:55):
Wrote an Android app,
with that. And it was, an
interesting experience. I don'tknow that I've learned enough to
really have a full opinion on ityet, but it was definitely,
another option that's out there.And I think that I would have to
get into truly building with atool, truly building a full
(14:15):
project in something before Ican commit to saying, oh, yeah.
This is definitely the way thatI'm going to do it.
Peter (14:21):
Yeah. And and thanks to
the the live chat room here.
Someone said try skip tools.Yep. We'll put links in the show
notes to the 2 episodes wherewhere I interviewed them, the
guys behind it.
We did one when they were stillsort of working on it and then
we did another one when theyreached their major milestone,
which was essentially the firstrelease. And, yeah, I certainly
(14:42):
tried it, in the early days andand found that it was, you know,
surprisingly easy for me as aSwift developer to to do that.
So I have no doubt that thatit's even better now, and and
that is certainly one that I,you know, would recommend, not
just because, you know, becausethey've been on the show but
because, hey, you're you'rewriting in Swift. Right? I mean,
(15:05):
it doesn't get better than that.
So yeah. So there's that and andwe'll talk about this no doubt
in the future. You know, you'reyou're free to change your
commitment at at any stage
Geoff (15:16):
at this point. Of course.
Yeah.
Peter (15:18):
Yeah. For me, I I'm I'm
with you. So, you know, number
1, I'm interested in as I havespent less time coding in sort
of the latter half or latterquarter of of 2024, it gave me
time to go look at some otherthings and I'm I'm definitely
(15:38):
interested in the marketing andand and like you say, stepping
up that side of it and andunderstanding that more and, you
know, so I think it's once youget a couple of apps out in the
stores, you look at things andyou go, okay, now it's time to
see how I play with the themarketing side and promotion and
(15:58):
and and learn some of that.Right? I don't anticipate to
become a, you know, overnightgenius on this, but I've
certainly neglected in the past.
So that that is one for me.Another thing though, actually
we were talking about in the inthe pre show here, as as I'd
mentioned, you know, I finallyhave released the Android
version, built with Godot of myEnder's Hurdles app and the the
(16:23):
iOS one is ready. I just haven'treleased it. So that essentially
has has moved me on fromSpriteKit to a cross cross
platform game tech right there,and there is Swift available in
in some flavor for, Godot. Andthe reason I say it like that is
because I have not looked at itin a long time at this point,
(16:46):
and I think that it sounds likeit's time for me to revisit that
and see see how much of anoption Swift really is.
If I could use like Godot withSwift in a way that didn't
require me to jump through toomany hoops, that would be an
interesting option. So I thinkthere's some learning to be done
there. That's kind of mylearning goals for next year. If
(17:06):
I can achieve even just bettermarketing, you know, sense and
and promotion, that would bethat would be a win that I'd be
happy to walk away with. As faras like any certifications, I
don't have any plans and and thereason for that is not that I
don't value certifications oranything that people go for, but
(17:27):
I think that personally I findthat technologies still move so
quickly.
By the time you're certified insomething, it it it's not as
useful as you might think.Right? Like, I remember when I
got all of my certifications forFlash, and then it's like, well,
that's dead.
Geoff (17:44):
Yeah. I'm not planning on
getting any certifications
because there's not much use forthem in an indie development
world, but, sure. If somebodywants to pay for me to get
certified in something, talk tome.
Peter (17:56):
I I I can see value for
it in, like, a freelancing
contracting type scenario, but Ithink their endorsements are
still more important thancertifications. Right? Hearing
what, you know, people you'veworked with, clients or whatever
actually, you know, think ofyour work and how useful it's
been, that to me still means alot more than, hey, I'm fully
(18:19):
certified in all these things.Right? To me, a lot of
certification stuff is, yes, Ican pass tests, Right?
Which okay. That's great, butit's not really as beneficial as
what I would say real worldexpertise. Right? Meaning, you
know, we've said this before.Yeah.
(18:40):
Great. You can you can quote allof the foundation library and
and how does that help you inlife. Right?
Geoff (18:46):
It used to be really good
for free drinks at WWC.
Peter (18:49):
Oh, I'm sure you were,
you know, like, hey, tell us
that one again about, you know,insert function name here. Yeah.
Geoff (18:58):
So what about being out
and about in the world? Are you
planning on going to anyconferences this year? And if
not, why not?
Peter (19:12):
Yes. Okay. So, folks are
like, what's so funny? So I I
still plan to to go to, aconference this year. I I do
plan to try and make it to deepdish.
And I say the reason I say itlike that is not because it's
(19:33):
like, oh, I'm not gonna or I'mabsolutely gonna. At the moment,
work wise, there's a lot goingon, way more than you would
expect or had planned for atthis point in the year. So,
that's why you plan
Geoff (19:47):
for the the conference
now because it's
Peter (19:51):
Well, I was
Geoff (19:52):
like couple months until
you say I
Peter (19:53):
was I was gonna say
Geoff (19:55):
You say now, hey. I'm
gonna do this thing in 3 months,
4 months, I think.
Peter (20:00):
Well, that that is how it
started. Yeah. And then and then
it became complicated.
Geoff (20:06):
Because because if you
wait until the last minute, then
it's gonna be complicated lastminute, or you say now.
Peter (20:11):
Well, no. I know. So so
at the end of the day, the
problem is gonna be that it'sgonna cost more than it should.
No no question there. But I I Istill want to find a way to make
it, because I hear some otherfolks I know might be going.
What about you?
Geoff (20:28):
Yes. I I also am planning
on on making it to,
DeepDishSwift. I do currentlyhave a ticket. I have plans to
be there. So,
Peter (20:37):
so you planned ahead. You
you you Exactly. You're like,
well done. Oh, that's right.Because you don't have a day
job.
Geoff (20:42):
I mean, I have a day job.
It's just I'm the person who
I've asked to do stuff.
Peter (20:46):
Yeah. Exactly. Your your
your person is a lot more will
will work with you.
Geoff (20:51):
Right? Hey. Can can I can
I just, like, sit here and talk
about all of the benefits ofsending your employees to to to
to conferences so that your bosswho's listening to this is like,
I should totally send my my,employee
Peter (21:04):
to this conference? You
you
Geoff (21:06):
you should, you should
send Peter to the conference so
that I can beat some sense intohim, and he'll come back being a
better developer.
Peter (21:13):
So something else that
I'm planning to do this year
that I've actually alreadystarted okay. Granted I've only
released 1 episode, but, some ofyou may be familiar that I I
have another podcast, called PWPodcast. I'll put a link in the
show notes. And over theChristmas holiday here, I had
this idea of, taking basicallyall the questions we always get
(21:37):
from folks about, I wanna makean app, I wanna start an app,
and you know, how do I do that?And do I use this?
Do I use that? And I thought,you know what? I've never put
together a small mini series.And so on that podcast, I'm
putting together a small miniseries of, you know, basically
what you should do to as youwant to make an app. Now it's
(22:00):
gonna be, you know, I'vereleased one episode, which is,
out there and it's gonna beabout all the things, related to
the making of an app withoutdiving into things like code in
that because I think a lot ofthe times those are the areas
people don't think about.
You know, so for example, I'llI'll give you some quick
(22:22):
highlighters. They are they aregonna be short episodes. My goal
is to keep them all under 10minutes, so they're quick bites
and, you know, things like,okay. What's the first thing I
should think of? You know, so inthe first episode, I spoke about
well, the very first thing youshould think of is you should
have an idea.
And by that, meaning have anidea, you know, commit to the
(22:46):
core idea, think about your youwhat's your user gonna look
like, those kind of things. Andthen in future episodes that I'm
working on at the moment, youknow, working through that
process where and as I clearlystate, you know, the important
part is not picking the tools.Right? The important part is
what is this app gonna do? Howam I gonna do this app?
(23:07):
What are my time frames? Youknow, and then, okay, now I've
got this idea. What are thefeatures and committing that and
and saying this is my one orelease and and basically taking
it through to the end ofcreating an app and getting it
to to submit to a store. Now I'malso doing it in a way that it
(23:27):
applies to mobile apps, and I'msaying mobile apps not
necessarily platform because theprocess should be the same. And
that's kind of part of what Iwanna get across here, and web
apps and that as well, which isdon't focus on your selection of
the importance of tools andlanguages and so on, focusing on
the product itself.
Right? So I have a small seriesthat I'm putting together on
(23:50):
that. Again, I'll put a link inthe show notes. The one episode
that I've put out there, thankyou to everybody, who gave me
feedback on it already. Greatlyappreciate that and and you've,
you know I I asked folks, hey.
If you wanna hear this, tell meand I'll keep working on it, and
they did. So that's what I'mgonna do. It is a podcast, but
(24:11):
at some point I'm thinking theremay well be a video version as
well as we talk about somethings. I'm still kicking that
around, you know, I don't wantit to just be a talking head,
right, because I think at thatpoint it should just be audio,
but that's where I'm at as faras, all of those things. So as
someone mentioned in our chatroom here as we're recording
(24:32):
this, yeah, other things, legal,right, internationalization,
accessibility, all those otherthings that might not sound
super cool to a developer, butat some point you have to deal
with that.
Right? And so that's what I'mlike if I if I tell you ahead of
time, here's your checklist, youget to work on that over time
while you're building the app.That's kind of the idea here.
(24:54):
And for those of you who arewondering, the reason it's not
on the CompileSwift podcast is,you know, we try to keep this to
Apple orientated, developmenttopics of which, yes, everything
I just described does apply toApple, but, again, I'm making
this one generic enough to applyto other platforms including web
and so on, and so I I decided,you know, this should probably
(25:18):
exist by itself on my other pod.
Geoff (25:21):
Peter regrets adding me
and he, was like, I need to get
a podcast that's away from thatchannel.
Peter (25:26):
I didn't feel you needed
to say that. I'm hoping that
that subtext came through. And,
Geoff (25:32):
of course, we couldn't
have any of our years, much less
2025, without our lovelycommunity, both from Twitch
chat, from our developerDiscord, all of the above. And
so we're gonna leave you withsome of the plans from some
other people. We've asked forrecordings of anybody's ideas
for what they're doing in 2025,and you're gonna hear from them
(25:55):
now.
Jared (25:56):
Hey, everyone. My name is
Jared Hall, and you can find me
on the dev club discord as monon zed. Last year, I realized
that I often integrate withSlack to get important updates
about my projects on the go. Itwas always a pain to load up
those big analytics websites onmobile to see user growth and
app activity. I wanted an appfor it and be notified with push
notifications.
(26:17):
I've been working on a SaaSplatform called API alerts. It
lets you easily send pushnotifications to your device
from your various projects. Youcan find it at API alerts.com.
With API alerts and itsintegrations, I can easily see
on my device when I get a newuser, a payment comes through,
or a CI pipeline deployed, orfailed. This has been incredibly
(26:37):
useful in both my solodevelopment and in my day job
where I no longer need to checkon things.
I'm notified quickly and canreact to them. One of my
favorite user stories is from afriend in sales who integrated
the JavaScript library into hiswebsite's contact form. He gets
a push notification wheneversomeone fills out the form. And
by adding their phone number asa link, he can tap the
(26:58):
notification on his phone andcall the customer directly.
Their users are pretty amazed toget a callback in sometimes just
a few minutes.
A big goal of mine is to set upintegrations with other services
like Zapier. If they send that,home automation, Google Home,
and more. I'd love to see itused by people other than just
us developers. This year, I'mfocusing on adding payments,
(27:20):
teams, and integrations to APIalerts. While spilling out my
web panel using React, I'm alsospeaking out event destinations
other than push notifications soyou can receive high priority
events as a text message, email,Slack or Discord, even a phone
call.
Over the past 6 months, Ireluctantly rebuilt my swift iOS
app using Android's composemulti platform. Whilst there
(27:43):
were initial challenges, it cametogether quite nicely and I can
continue to call native swiftcode when needed. While it's
still new, it's proven to bequite a time saver as I attempt
to grow this platform. Lookingahead, my long term goal is to
make my side hustle a reality.I'd love to go full time as an
indie developer, so everything Ido this year is working towards
(28:03):
that goal.
Cheers.
Daniel (28:05):
I want to like what I'm
doing. I wanna like how I'm
doing it. This will require meto slow down and raise my
awareness. Hello, everyone, andthank you, Peter, for inviting
me to have a little blurb onyour podcast about 2025. I'm
really excited about 2025because 2024 was such a huge
(28:26):
period of transition for me, andI feel like now I have the
juice, now I have the tools tomake 2025 something really
special.
So question 1, I'm a developerliving in New York City,
developer of all kinds, iOS,Android, web, back end, DevOps,
and I also develop songs,videos, and myself. I currently
(28:49):
have one client and one passionproject. I'm turning that
passion project into a businessthis year. You can find me on
Twitch, Daniel Sincere. You canfind me on the web,
danielsincere.com.
You can find me on YouTube,Daniel Sincere, or on the App
Store by searching Underway.Question 2. Underway is my focus
(29:10):
this year. I'm working on backend tasks in order to deliver
some new features to users. I'mintegrating with new third party
tools like Adapti and Auth0.
I don't like preannouncing userfacing features until they're
ready, but what I'm working onhas been asked for by users, and
I'm pretty sure they're gonnalove it. I think, I think it's
(29:32):
gonna be so good that it's gonnabe worthy of going to the pro
tier. Question 3. I'm learninghow to turn Underway into a
business this year, and I'mpaying for coaching to help me
get there. So far, she's beenincredibly helpful.
Having someone to verbalize mygoals to, but also, they are
cheering me on and keeping me ontrack with my goals. 10 out of
(29:53):
10 would recommend. Question 4.I am dropping adding more stuff
to Android. Gonna focus on iOStill this business is a
business.
I am also dropping adding inmore side projects as the years
go on. This is something that Ilearned through the coaching is
that just like our lives have ahero's journey, so do our ideas.
(30:15):
And when an idea goes throughthe pit of despair, that's not
the time to go find a differentidea to start over with. That's
the time to really commit andfigure out how to make it work.
That's the time to find a way tofind a way, Or not.
You can do whatever you want.For for me, I'm pretty sure that
Underway resonates with me stillbecause it is an app that I use
(30:38):
every day because I ride thesubway every single day of the
week. Question 5. My goal isexcellence. You can expect more
videos from me this year andmore features from Underway this
year, in addition to polishingwhat I already have to make it
even more excellent.
And I'm starting to understandthe idea of how expressing
myself is of service to others.
Dalton (31:01):
Hello. My name is Dalton
Alexander. I've been a Swift
developer since 2019. I releaseda few apps on the App Store.
Symbol Grade is my most popular.
It's a browser for SF Symbolsthat developers can use to plan
out their projects, favoritesome symbols, change some
(31:21):
colors, kind of see howbackgrounds work with them. It's
a very nice app. I plan to add afew features, make it a little
more robust. It began as an appto learn SwiftUI as well as the
app store, but I've beenenjoying, friends using it to
learn more about SF Symbols.Currently, my role with Milk
(31:44):
Group, which is a dairy softwarecompany, is writing UI tests.
I'm using the Appium frameworkto do so. That interface is also
using swift testing. I hope tohave a package out soon that can
explain more about the that aswell as provide some UI
(32:05):
automation for multi platform UItest written in Swift. My GitHub
is dldashalexandre. You'rewelcome to fork any projects
I've been working on.
Contribute if you feel so kindas well. Just look around. It's
some fun stuff I've found andlove to share. Thank you.
Peter (32:32):
Alright, folks. So that's
kicking the year off here. That
that is, our plans. Keep ushonest. Come back.
Stay with us throughout theyear. Right? And at the end of
the year, let's see how well wedid. And and for for anyone who
has sent us a submission, right,we're gonna hold you all
accountable. So, it's a matterof record at this point.
(32:52):
So thank you everybody for this.I think it's gonna be another
good year. I'm I'm not gonna sayit's gonna be the fastest year
ever because Apple's probablygonna claim that but, thank you
for joining us for this newyear, this new episode. I am
confident it's gonna be the sameanswer as last year. But just in
case, Geoff, where can I findyou?
Geoff (33:10):
Yeah. You can find me at
cocoatype.com and all of the
various socials also ascocoatype or cocoatype.com.
Peter (33:18):
You can find me at
peterwitham.com and this podcast
at Compileswift.com, of course.That's it folks. See you in the
next one.
Geoff (33:25):
Yeah. Bye.