Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Peter (00:02):
What's up, everybody?
Welcome to the episode of the
podcast with these people. Now Iknow that's not the usual
introduction. All will beexplained or at least we'll try
to convince you. The otherperson is still Geoff.
How are you doing, Geoff?
Geoff (00:21):
I am still here,
surprisingly.
Peter (00:24):
Alright. And and I'm
still here, not surprisingly,
and probably much to everybody'sdisappointment. So this is a
slightly unusual episode. Firstof all, let me make it clear
because I know that there's beensome recently. This is not one
of those announcements like alot of other podcasts.
Well, this is the last episode.No. That is not what this is.
Geoff (00:45):
However episode was the
last episode.
Peter (00:47):
The last episode was the
previous episode. This is the
next episode that is now or backthen depending on what you
Geoff (00:54):
What what I meant was
last episode was the last
episode of the compiled swiftpodcast.
Peter (00:58):
That that that could be
true, but it's not the last
episode of a podcast. And Fairenough. And we're gonna explain
everything, folks. Right? If youthought the end of lost was
confusing, there ain't nothing.
We got this. Okay. So we'regonna be slightly different in
this episode. We're gonna beexplain some changes or the the
(01:21):
other way of putting it is whatthe hell did Peter do this week?
That's the other way to toexplain it.
So it's kind of one of those,alright, everything was renewing
as far as, services andeverything else for the
podcasting, this week. Well,actually the what's today? Yeah.
The day of recording this, todayis the day that they just billed
(01:43):
me. So it is also afforded timeto sort of reflect upon where
we're at, where we think wewanna go, or or maybe more
accurately me.
I I I guess we should say I'mkind of the cause for all of
this. Now don't worry folks.There's still gonna be a swift
podcast out there. Let us makethat very clear. Right?
(02:04):
We're not suddenly gonna becomelike one of those true crime
podcasts or something like that.But we are pivoting in a good
way, I think is how I woulddescribe it. So I'll I'll start
by diving into this. Right? Whenwhen this podcast was first
invented and the idea came alongand as I say on the website, it
(02:26):
was to serve a purpose that Ineeded and hopefully to serve a
purpose that other people neededas well.
At the time, Swift was obviouslybrand new and wanted to put
something out there. Now overtime, there has of course been
changes. Right? You know, Swiftis, there there is, you know, a
(02:48):
lot more to making apps thanthere used to be. Right?
So when I started this, to me,the idea was pretty clean-cut.
Oh, yeah. Apple's new languageis Swift. I want to learn Swift.
Hey, I'd love to learn how tomake podcasts better, so I'll
make a podcast about Swift.
And that's how it stayed for along time. And then, a co host
(03:11):
came along and now I've caughtyou up to today. I know pretty
pretty short history. Right? Butit's not what it used to be And
there's a lot of other tools, alot of other things and we'll
talk a little bit about whatI've noticed in the metrics as
far as what people seem to beinterested in.
(03:32):
But, Geoff, you wanna you wannajump in there as far as, you
know, how we've seen theecosystem change and and why we
think there's scope for more?
Geoff (03:42):
Yeah. And I mean, this is
obviously something that exists
well beyond podcasts, but it hasbeen the case over my entire
career certainly that mobile wasthis humongous thing. It was it
was the thing. And, you know, wehad a lot of ourselves put into
that, a lot of knowledge putinto that, and there were a lot
(04:03):
of people wanting to learn andwanting to know a lot about
mobile. And especially over thelast two or three years, it
definitely seems like mobile haskind of hit a point of maturity
where it's no longer the hot newkid on the block.
And so what we're looking at andwhat we're seeing is, you know,
(04:23):
a podcast that is very muchfocused just on Apple, just on
iOS, just on one particularlanguage is not really something
that people are findingcompelling these days. And it's
not just podcast. Like, I we'veseen this with conferences.
We've seen this with in personmeetups. We've seen this with
all kinds of things.
And so in order to keepproviding quality content, we
(04:48):
need to kind of expand our scopebeyond just a very small
specific niche.
Peter (04:53):
Yeah. And I think an
important point there that you
hit on is now that Swift ismature, right, I think, okay,
I'm not gonna say SwiftUI, forexample, is mature, but it is
certainly stable for one of abetter way of putting in, is
along with that comes theproblem of there is not
(05:17):
something to talk about everyweek. Right? There's not
something new. There's notsomething radical shift.
There's not controversy. There'salways controversy. You know, so
there are times that we struggleand and we have ironically, we
do have a list of topics. But asGeoff and I have been looking at
(05:38):
the topics recently, it's kindof been one of those, yeah, we
don't really want to talk aboutthat. It's not that interesting.
And and a key part driver for meand I'm I'm gonna from my
perspective is it has to besomething I'm interested in for
me to be able to really sort ofpassionately dive into it for
one of a better way of puttingit because I think that that
(06:01):
makes that comes across in therecordings. Right? If you don't
sound interested, people pick upon these things. And I I didn't
want that to be a thing. And atthe same time, I didn't want to
stop making the podcast becauseI don't want to speak for Geoff
here but Swift is still my mainlanguage and it is the language
(06:23):
that I use to make apps, right,and everything else.
And it is very much the thingthat I I live and breathe a lot
of the time. Stillprofessionally make apps. But
there is not enough interestinghappening every week to keep
telling folks about it. Right?And that was part of the reason
that we switched to a two weekrelease schedule because it gave
(06:45):
us time, not only time to do ourprojects, which you've heard us
talk about in other episodes,but also time for us to gather
up, do our research and, youknow, the community is a big
part of this as far as whatthey're interested in.
And we also have otherinterests. You know, I think
(07:06):
it's a fine line, Geoff, right,between defining something as
another interest and this isanother tool in the box that I
use to get the job done. Right?Mhmm.
Geoff (07:19):
Abs absolutely.
Peter (07:20):
Yeah. And so we thought,
you know and and and folks
who've followed some of my otherpodcasts that sort of I'm doing
this series about making an appright now and that was also part
of what got me thinking aboutthis was Yeah. I want to talk
about some of these other toolsthat I use to make apps, some of
these other approaches, thewhole app production ecosphere,
(07:44):
I guess, is how I would describeit. Right? And it became very
apparent in the metrics when Ilooked at them.
The folks out there listening tothis podcast also have interest
in these because see the, youknow, the numbers bless you
audience. Thank you so much. Thenumbers are going up all the
time. It's fantastic. And thatactually applies a lot of
(08:06):
pressure as well to keepdelivering and keep delivering
good content.
And it also tells us that youknow we could sit and recite
code until the end of the daybut I don't know about you Geoff
but I I couldn't listen tosomeone just talking about, you
know, like, oh, and and then
you go in here and it's this anddot that. And that's not where
(08:28):
I'm at when I'm listening tothese podcasts. Right? It's more
about listening and being youknow, almost feeling like you're
listening to someone have aconversation with you about app
development as opposed to, youknow, this is the code I wrote.
You you know what I mean?
Geoff (08:44):
Yeah. Pod podcasting is
not the medium for which to
explain in-depth technicalperspectives. You know, it it's
it's very hard to read code outout loud in a way that makes
sense. And so, yeah, we'vedefinitely already kind of been
pivoting away from that and moretowards the, you know, general
best practices, general tooling,general, like, personal and
(09:09):
career growth and that kind ofstuff going forward. And trying
to look into more of thesegeneral things and less focused
on the specific implementationof it in one particular language
for one particular platform.
Peter (09:25):
Yeah. Absolutely. Because
we're also very aware as as
probably a lot of long termdevelopers are out there, it is
part of the process. And we knowcertainly from friends of ours,
right, that we we've hadconversations with, just up to
the other day. You know, makingapps and releasing apps, it's
(09:48):
not hard to make an app.
It is very hard to make asuccessful app. It can be very
hard to get it successfullythrough app review and add into
the store and to get peopleusing it. And we have certainly
seen from the feedback thatwe've got people are very
interested in these thingsbecause, you know, again this is
(10:08):
all part of the journey. Right?And this is what we're sort of
getting at here is as we gothrough these other parts of the
journey that we've not reallyspoken too much about before, we
are very conscious that otherfolks are going through them too
and clearly want to have moreinformation out there and
conversations about it.
Fantastic. That's why we've gotthe discord. That's why we do
(10:30):
this. This is why we do our livestreams and the recognition that
it's not just the Swiftlanguage. Right?
There there there's all theseother things like Geoff, for
example, I don't know how manystreams you've done at this
point where you've been usingTwist, for example, but it's an
integral part of your processfor making apps with Swift.
Geoff (10:51):
Yeah. I mean, and and
it's not just even specifically
things that are for building iOSapps, you know. I'd love to
spend more time talking about myIDE of choice. I'd love to spend
more time talking about, youknow, AI tools, the abilities
that you can use with them. Andthat can be true whether you're
(11:14):
building a mobile app.
That can be true if you'rebuilding a desktop app. That can
be true if you're building aserver side back end or a
website. And so it really I Ithink it limits us to say we're
only gonna talk about oneparticular language, and there
are so many things that we candiscuss that are helpful. Yes.
(11:34):
Certainly to people who aredevelopers in Swift doing mobile
development day to day andthings that are still helpful
even if you have a day job whereyou're doing something
completely different.
Peter (11:47):
Right. Right. I mean, you
know, how many times have we had
folks say to us, hey, I need todo a back end like you say for
for my app. I gotta call someAPIs. I gotta do some kind of
server storage, some kind ofserver setup.
What server side language shouldI use? Should I use, you know,
like, we covered Vapor and,Hummingbird and all those kind
(12:09):
of things. And so we wanna openit up to have those
conversations and to say, youknow what? It is perfectly fine
to keep asking those questionsand and we we certainly have
plenty of thoughts anddiscoveries ourselves. I'm I'm
currently working throughdiscovering AI, for example.
So, you know, but we want totalk about that because
(12:31):
everybody's talking about thatand therefore there's
conversations to be had. I wantto learn from folks. And so we
want to share that informationwith them and uncover those
topics. So we will stillabsolutely Swift and and Apple
platform development is verymuch our core thing. It's not
(12:51):
gonna go away but we are goingto be covering these other
topics as well.
So if there is, for example, anepisode that you're like, I'm
not really interested in that,skip it. Catch the next one, I
think is what we're saying.Right? It gives us an
opportunity to, I guess,demonstrate what we know, but
(13:12):
also demonstrate that there areso many other parts to the
equation of of making apps.
Geoff (13:18):
So as you might have
noticed on your feed or in your
favorite podcast player, we arecurrently named the untitled app
developer podcast. And we leftthat very much as a placeholder
to kind of announce this andsay, yes. We're expanding our
scope. We are no longer going tobe the compile Swift podcast
(13:38):
because we are no longer focusedsolely and specifically on the
Swift language. But we'reobviously not gonna be the
untitled app developer podcastforever, and that's where you
come in.
We would like you, as acommunity, to suggest, like,
what kinds of things do youthink of when you think of app
development as a whole? What arethe things that you think of
(13:58):
when you think of our podcast?And reach out to us either on
our Discord, on our livestreams, on our social media, on
Apple's podcast reviews, withany ideas that you have for an
app development podcast name,what we should be calling
ourselves going forward. We'll,probably not put this up exactly
(14:20):
to a vote, but we would love totake whatever ideas you have
into consideration.
Peter (14:25):
Yeah. Absolutely. Because
for for better or worse, you
know, when it started out andfor the longest time, it was
just me. And therefore, youknow, at this point, so many
folks come to me and know me andthey're like, oh, you're
compiled Swift. Yes.
That that is part of the problemwhen you're doing something like
(14:47):
this is the branding works sowell, but it works so well to
brand it as me, which was neverreally a goal. It just worked
out that way. But at this pointand and as with our discord,
right, I never I I didn't wantit to be a me thing. I Part of
(15:10):
the reason for the name compileswift was, well, okay, firstly
it's catchy, right? Butsecondly, that it's right in
there, compilation.
Right? It it I wanted it tobecome a community thing which
it very much has, thanks to thelisteners and, you know, like
the dev club, discord and thingslike that. And therefore, I want
(15:32):
to move this into a more of a,you know, yes, we host it. We do
it. But it is a conversationwith folks.
It is a two way thing, and andto get away from, oh, the
compiled swift guy. Right? Imean, don't get me wrong. It's
not hurt me at all. Far from it.
(15:52):
But I don't want it to be, youknow, the thing that is Peter.
Do you know what I mean? And so,that's kind of what we're
looking for here and and alsorecognition because it's it's
not right that for example, youknow, poor Geoff. He comes
along. He's the co host.
(16:13):
He's great at it, but it's likebut it's compiled swift and he's
that other guy. And and and andtherefore we wanna sort of fix
this glitch. Right? That's itfolks. So reach back to us.
Right? There's gonna be links inthe show notes as usual. Best
place to get us is always gonnabe on the discord where all the
other fantastic folks areincluding a lot of the
listeners. But however you wannado it, please reach back to us.
(16:37):
We are here for you.
That is part of the goal and thedriver for this. And with that,
that is what we've got in thisepisode. Geoff, let's do it one
more time for the last time onthe what was Compile Swift
podcast, now gonna be somethingelse podcast. Where will they
continue to find you?
Geoff (16:54):
Cocoatype.com on all of
the socials and everything.
Peter (16:59):
There you go. You can
find me. I'm still I'm still on
compileswift.com. That's theirony. We also need to find a
new domain name.
So, maybe. We'll see. And youcan reach me at peter Witham dot
com. But again, go to the devclub discord. That's the best
place to get us and everybodyelse with a conversation.
(17:19):
Take care, folks. We will speakto you again very soon. We
promise.