Leo Dion (host): Before we begin today's episode, I wanted to let you know Bright Digit needs your help.

We're looking for developers to help with several products, of course, I mean iOS development,
but also watchOS, Vapor, macOS, HealthKit, SwiftUI, and not just stuff in the Apple and

swift space, but also web development, vueJS, TypeScript, Docker, Postgres, and more.

If you are interested, email me your portfolio or resume to leo@brightdigit.com.

Again, that's leo@brightdigit.com.

I'd love to see what you can do and how you can help with our team, but there's more.

I also have some availability for work as well.

If your team is strained by too few people or just need someone with my
expertise to guide your team, reach out to me at leo@brightdigit.com.

That's right.

Email me leo@brightdigit.com.

We have some availability to help your team.

So if you just need somebody for temporary part-time contract work, let me know.

I'd love to see what I can do to help your team.

Thank you for your time, and I hope you enjoy the rest of today's program.

Welcome to another episode of Empower Apps.

I'm your host, Leo Dion.

Today I am joined by once again at Tim Mitra . Tim, thank you so much for coming back on the show.

I really appreciate it..

Tim Mitra (guest): Hey, thanks for having me again.

Yeah.

Leo Dion (host): In case people don't know you, I'll let you go ahead and introduce yourself and your podcasts.

Tim Mitra (guest): Sure.

I am an again, I'm sort of a creative type.

I'm a maker tinkerer.

And for the last 12 years or so, I've been basically working in
iOS a little bit of Mac, but mostly iOS primarily around the iPad.

Similar to you.

I started because of the iPad.

it had been doing like development before that, you know, apple reseller, that kind of thing.

But but the iPhone creating, you know, magic for people on the iPhone was
sort of what drove me on the iPad obviously, cuz it was a larger format.

Yeah, so, you know, spent some time, early time teaching people how to do iOS when it was a new thing.

And yeah, I've had a chance to work with Apple a few times in a few different careers, but,
doing iOS and I think part of the, the idea behind the podcast, we do a couple of them.

I do one on sci-fi centered around Star Trek and other, but all kinds of other sci-fi.

But the main PO podcast I think people might know me for is more than just code, which is about iOS development.

And it's sort of our way of giving back to the community in terms of like, you know, some knowledge that we have.

App, app, reset, app, app developers, engineers, that kind of stuff.

And yeah, just, you know, we do it for the people

Leo Dion (host): and of course I was recently on there.

We'll have a link to that episode where we talked about a bunch of stuff, including vr Yeah.

And floppy disks and stuff.

So you'll definitely wanna check that one out.

What are you currently working on right

Tim Mitra (guest): now?

I'm currently engineering manager over at Spot Hero in Chicago.

And as well as working on some of my own sort of apps.

I'm trying to do refactor a couple of things using SwiftUI and
iCloud, which iCloud and core data that we've talked about before.

Yep.

But to be honest with you, I have, I'm currently obsessed with the Red Dead Redemption 2.

I've been spending way too much time playing that I should be writing code at night.

But, you know, I tend to write code at night and that's usually
what my hobby is, or 3D printing and that kind of stuff, but yeah.

Yeah.

I gotta gotta admit, the PlayStation's got me hooked, right.

Leo Dion (host): Isn't.

Became like three years old.

Tim Mitra (guest): It's many years old, but it's, it's actually really well done.

It's, it's it's funny, like I was thinking about that last night.

You know, I remember being a kid in a bowling alley in St.

Catherines, Ontario, or actually I guess Toronto.

Seeing Pong for the first time, and then shortly after Pong we
got, you know, Pacman and then, oh, space Invaders came after Pong.

Right.

So, and those, and you know, so I'm thinking, you know, like in the history of game development, like playing
Red Dead Redemption Two or the to Raider titles or Uncharted, you're like, if you're playing, you're in a movie.

you know, in a sense, like the music's there, the, you know, the guitar, little subtle, you know, western guitar
in there and, you know, you're running around on a horse and everything looks pretty, you know, it's animated

admittedly, but it looks pretty realistic, you know, and, and we've come a long way from like, sort of eight bit
crappy graphics, you know, on a C R T screen, you know, to, to like, you know, 4K stereo surround sound, you know.

Leo Dion (host): Totally.

Yeah.

So, so we had a couple of things we wanted to talk about today.

One of the things you wanted to talk about was what you think most people are missing when they're developing an app.

As far as like, just kinda like buzzwords or trends that you see . That you think could be possibly misleading.

And what you think people should really be be doing when they're building.

A big project, I guess, or

Tim Mitra (guest): even a small Yeah, I, I think it's true of any, any project you work on.

I see.

and this is based on a lot of stuff that I see on, on the interwebs
and the socials on the Twitter and the, and the Mastodons and Facebook.

Well, not so much Facebook, I don't talk to engineers on Facebook, but . I do talk to
engineers who work on Facebook, but I don't talk to and people on Facebook about that.

But yeah, I think the, the, you know, you hear a lot of things like, especially from
new users who are just getting into the game, like, what should I, should I do UIKit?

Should I do SwiftUI?

Should I, you know, should I do Core data?

Should I do react?

You know, should I do flutter?

What should I learn?

. And I mean, the reason why my podcast is called More Than Just Code is literally because
I believe that there is more than just writing code to building an an app, right?

I've said it many times before that, you know, it's, it's writing the code, it's, it's creating the user
experience, it's creating surprise and delight is what Apple would like us to do with our apps, right?

So there's a lot of, a lot of avenues to building an app.

You have to think about marketing or even a building, a bu it's
kind of like building a little mini business, if you think about it.

I mean, if you're.

for the sake of putting an app on the app store, which I've done, I've
just put apps up there just for the sake of, of going through the exercise.

You know, then it, it comes down to, you know, you have to evaluate the, the why.

Why are you doing this?

What's your reason?

Are you doing this because you wanna make a living at it?

Are you doing this because you want to, you know, build a portfolio, whatever your intent is.

And that's true of any sort of creative process.

And I believe that writing code and making apps is a creative process.

You'd have to sort of evaluate what your intention is.

Are you just doing it for fun?

Are you doing it for profit?

You know, what's your motivation?

I'm very empathetic to the user or the customer's, clients, you know, and, and
calling them users is sort of an engineering term, but maybe we should, we should

some, some, some companies I work for, they, they kind of change that terminology.

We're not allowed to call 'em users, but.

because it kind of takes the humanity out of them.

I'm a big advocate for security and for accessibility as one of my big pet peeves.

And especially since, you know, I'm, I'm wearing an accessibility
device, a pair of glasses, you know, got the gray hair going here, right?

So, so, you know, I use larger type, you know, so, I've been, you know, I wasn't really big into the
dark mode, sort of, you know, the, the xcode with your screen color reversed and all that kinda stuff.

I still code in, you know, plain old boarding, boring white.

But I like, you know, I like it sunset that my, my devices all switched to a dark mode, right?

I've gone through all my websites.

I've added dark mode to the website, so that, , you know, at
that time of day everything switches and, and that kind of stuff.

But I think that there's, I think one of the biggest pieces that I find missing in a lot of teams and
a lot of apps is that there's a very large percentage of the world that have some sort of impairment

in terms of either visual or auditory or, you know, there's, even as you get older, you, you know, we.

We all get to a point where we need some accessibility devices,
and I think that's a huge thing that's missing in a lot of apps.

And, and of course, you know, there's also the.

The other, other side of the argument that you hear a lot about is testing, right About, about writing unit tests.

And it's funny cuz I, I saw a tweet on the weekend and from a friend of ours and I said,
you know oh, I thought we were developing apps, not, you know, delivering tests, right?

Because it seems to be, there's a lot of emphasis on is it testable code?

You know, are we, are we using mvvm simply for the sake of, you know, the story that it's easier to test?

Or, or are we doing that because it's a good architectural pattern?

I think those are questions that.

People need to ask themselves, but I remember something, I think it was Brent Simmons
said once about one of his apps is, God, don't look at the code under the hood.

The app looks great.

People love it.

You know, it ships, it does, does what it needs to do, but please don't, you
know, like I don't look, I'm embarrassed by some of my coding decisions, right?

Over the years.

And there's a few people who, friends of mine who's Mark, mark
on our podcast has seen my code and he shakes his head a lot.

But you know, the the the reality is, is, you know if it, and we talked about on my, I think we talked about on our show
the other day, the other day, about the 80 20 rule where, you know, , you don't have to focus on per, per perfection.

You should focus on progress.

Yep.

Right?

And, you know, sometimes you just need to ship a product to get it out the door.

So you know the 80% of the work is done.

Let's get it out there.

Let's see what happens.

. You know, I think another I've been fortunate to work on teams lately that have a good quality assurance group, right?

People whose specific job is to just test the apps, make, you know, do the dumb things that the users are gonna do.

I'm always amazed, like I was tease my QA people that they're stop breaking my app, right?

I wrote it, it's fine.

It works, right?

Stop, stop, stop finding the edge cases that, that make things grief.

But I think that, and it's funny because I've talked to a lot of teams.

and you know, I was doing the whole interview process for like 18
months and a lot of teams are, you know, I said, who does your qa?

Well, our, our dev, our engineers do the QA themselves.

Bad idea.

Like, you know, I think you need to have an impartial person who doesn't necessarily
understand engineering, who goes in and, and actually tests the device, test the.

To find

Leo Dion (host): the weakness?

Well, one of the things I see benefit of QA is like, I don't know, especially if it's a pretty big app.

I don't know every nook and cranny of that app.

Like, I don't know, oh, this was supposed to do this.

Oh, I didn't know that.

Like I could, I could develop something according to what I think
it's supposed to do, but I might not know what the user expects.

And I think that's like a big problem as far as like, The difference between QA and unit testing,
like whereas unit testing, it's just like, oh, just make sure my code runs the way I expect it to.

But sometimes what you expect is not what you are.

User or customer expects,

Tim Mitra (guest): right?

Yeah.

And, and the unit test just proves that your logic is sound and, and that, that, you know, it responds well.

And there's also automation testing.

I think that's a lot of something that people should consider as well is, is, you
know, what happens if I log in repeatedly for 10 minutes or something like that?

You know, those kind of Right.

That's where automation happens, right?

And that's where, I mean mm-hmm.

in.

. And the other thing too, that that's, it's, it's challenging as you,
as your point about QA is, you know, I just transitioned to a new team.

So it's an, it's an, a mature app that's been developed for a long time.

And I did the same thing when I joined the bank back, you know, six and a half,
seven years ago coming into a code base and nooks and crannies, I mean, like there

are parts of the banking app that I never looked at in the six years I was there.

Right.

I know.

I just know there weren't.

Right, right, right.

So it's difficult to sort of, it's difficult to sort of transition into a new team where the, the app is mature
and I think that may be a challenge, something that people should consider if they, if they move to a big group.

Right, right.

It's nice to have Greenfield development where, you know, the, the, we're
all only working as SwiftUI and we're only working with the new stuff.

It's, that's nice.

But the reality is, you know, in a lot of cases, you're supporting older devices.

You're working with, you know, design decisions that may have been, may
have worked a while ago, but don't work anymore kind of thing, right?

So, mm-hmm.

. Yeah.

Leo Dion (host): Yeah.

Excuse me.

One of the things I was gonna say is, As far as testing, like I think, I think there's a divide in the
community when it comes to the difference between like solo apps and apps that are built with large teams.

Mm-hmm.

, because I feel like there's kind of two, two sides that are like talking a different, like,
almost like a different language where it's like where you say, oh, like don't look at my code.

It's horrible.

Like, That's fine, I guess if you're a solo developer, but if you're on a big team where like
several people have to manage it, that's where having testability is even more important, I guess.

You know what I mean?

Tim Mitra (guest): Yeah.

Coding standards too.

I mean, like, you know, you have to agree on, right?

I mean, the biggest challenge of moving to a big team, especially as a, as an
individual engineer is do you understand the, the requirements for the team?

Not, not, I'm not talking about the accepting requirement for the ticket.

I'm talking about, you know, are we, are we running things like swift land?

Are we, you know, cause we, you know, we used to.

Swift link came along.

We used to use like a, there was a clang something, or rather we ran an xcode
to, okay, clean up our objective C you know, are we leaving, you know you know,

are, are, is, are we, you know, bringing up all of our declarations and methods?

Are we, are we not using extra white space?

Because white space makes it readable as a human.

Yes, but it's not as a team, maybe we decided to get rid of that.

You know, we don't, we don't want everything tightened up and less lines of code, as it were.

Cause white space accounts as a line.

Right.

But, And then, you know, are we using, like, I love the the, I
guess they're called Kodaco now, the Ray Weder, like folks, right?

They used to publish and they, I think they still do publish a swift like swift rules, sort of Swift guidelines.

They used to do an objective C guidelines as well, right?

Yep.

And sort of the team can look at those recommendations and agree.

And then is it, what's the one from Realm?

Is it Swift Lint?

JP and yeah, the JP

Leo Dion (host): wrote swiftformat.

Tim Mitra (guest): I think Swift format, that's what I'm thinking of.

Yeah.

The, the

Leo Dion (host): no or Nick Lockwood is swift format.

Realm is swift

Tim Mitra (guest): Lint, right?

Yeah.

Right.

Yeah.

So between the two of those, you know, there's sort of a, and you can accept their
suggestions as, as your rules, or you can, or you can use them as guidelines, as I said.

Right.

And then decide, your team can decide whether you want to do them and
what's nice about those automation process, and you can customize.

Yeah.

And these are part of your, your ci your, your, your continued integration, continuous development.

You can have those as scripts.

You can either run locally on your machine or you can have them on your build servers that Yep.

Run the things and reject your PRS based on that.

And dangers another important tool I think that, that is really nice that, you
know, it's like a, an extra engineer looking at, at the quality of your code, right?

So yeah, with the rules you put in danger.

Leo Dion (host): Yep.

Have you heard of strings?

Lint Speaking of accessibility?

No.

What's that one?

So strings lint is, it makes sure that you use.

String dictionaries and mm-hmm.

Localization for all the strings you use in your ui.

Oh, yeah.

Tim Mitra (guest): Language support's another important one.

Yeah.

Leo Dion (host): Yeah.

Which, if you're interested in accessibility and localization, we've done episodes on that.

Definitely.

Check that.

Oh yeah.

To check that one out.

Yeah, cuz I have, I have an app and it's like, I wanna make sure all my strings aren't just a, because
you know, when you first start you'll be like, oh, I'm just gonna write these strings and code.

But then eventually you could start using it'll warn you and say, Hey, you
should probably put this in a string dictionary since in your, it's in your ui.

So I haven't recommend checking that out.

Tim Mitra (guest): Yeah, I mean, I've always used localization and all
of my apps, the, my early apps were like supporting eight languages.

One of them was supporting 14, which was just crazy.

But, Yeah.

But, but, but it's, it's important.

I mean, like, you know, we're not, it is important.

We're not the, it's not English speak people and people who read, you know, left to right.

I have to think about that for a minute.

We're not the only people using your app, right?

Yeah.

So so that's another important consideration.

And obviously a market too.

I mean, you know, Canada's like a 10th the size of the United States in terms of
market, but then China is 10 times, 10 times the US or a hundred times the US I think.

Right, right, right.

So, You know, and it's funny cuz we, you know, in in, I worked in Canadian
banking and obviously Canada, our two official languages are English and French.

Right?

Right.

The majority of us speak English, I mean, sorry, French people, but I'm sure in some provinces
it's, you know, very French and some, some are bi fully, one province is fully bilingual.

Right.

But, you know, so you think, okay, well I need to add English and French into my app.

Right?

What we, what I, we didn't realize was a large, a very large percentage of our users are Chinese.

, right.

Okay.

So, so we had to, we, you know, in the banking app we added English, French, and then we started adding Chinese.

And that that sort of got, you know, a lot of, lot of people, I mean there were even
people in Quebec who are Chinese whose, whose fallback language is French, not English.

Right?

So these are things you sort of, that, that come up in, in, especially in larger ops.

I mean, I think I was, I was gonna go down this one rabbit hole was
that, you know, the banking app was u was used by 6 million people a day.

right?

Like that's huge numbers, right?

In terms of people who's using it, right?

So I mean, all the more reason that be accessible, support, accessibility, dynamic type and that kind of stuff.

Right.

Leo Dion (host): Do

you think one, one thing you wanted to talk about, and this gets into.

Other cultures.

Other languages as, yeah, multidisciplinary engineering.

What, what, yeah.

What does that mean, I guess, and how do you think that's helpful?

Tim Mitra (guest): Did I put that down there?

? . I think I, yeah, I think, I think what it meant by multi multidisciplinary
engineering was what they sometimes call cross-functional engineering as well.

Where Okay.

It's not just an isolated instance where you're in io.

You know, you may be dealing with you may be dealing, you're obviously dealing with endpoints
if you do any kind of, any kind of data stored on a network or any kind of user account stuff.

So I think what I meant by that was, was, I'd have to go back to my notes now but I think I meant.

Like, you know thinking about the engineering across CROK teams or across, across different silos, right?

In terms of like what you're, you're dealing with.

I mean, like I, in my own apps, you know, I write my own APIs, right?

So I do PHP and my sql.

Okay.

And so, so you, you know, you need, need to know those things and, and you
know, then if you've got Android support, you might need to know Kotlin.

You know, have somebody on the team who knows Kotlin, right.

And Java to be able to support those kind of things.

I think that's what I meant by multidisciplinary engineering.

It's not just again, the more than just code comment, right?

what?

More than just Iowa's code, I mean,

Leo Dion (host): Right.

I'm almost surprised at how many iOS tab don't know anything about backend development.

Yeah, but it, I mean, it kind of makes sense if that's all you've been doing.

But what do you, if you were an iOS developer, let's say I was a iOS developer, and I asked you Hey, what should I do?

What should I learn if I wanted to be branch out?

Or what would you recommend being

Tim Mitra (guest): first up?

Mm.

Well, I mean, I'm, I'm a fan of PHP from way back when, but the, I think,
you know, Python is an important language to Mark, mark Rubin from Morgan.

Just code would be telling you to learn Python for sure.

That's, I think, his favorite language.

I mean, there's things like Go GOs used a lot in, in backend work these days.

No, JS is another important one.

Leo Dion (host): Yeah, I was gonna say node, node type script, because that opens up a whole world type script

is

Tim Mitra (guest): sort of built on top of.

Or is it

Leo Dion (host): further Java built on top of JavaScript?

Yeah.

Right.

Yeah.

But anything like that where you can open the whole world, a web to you right.

Would be super, super useful.

Obviously I'm a big fan of backend

Tim Mitra (guest): paper and I was listening to your show with, with Sarah other today, swift.

Leo Dion (host): So like that's an option.

But I mean, that'll, that'll, I think that's good for teaching you
how, how to like, query a database or how to like build a rest api.

But as far as like learning another language, I think JavaScript type script would
be super helpful cuz then you can like do all sorts of stuff on webpages and things

Tim Mitra (guest): like that.

Yeah, I think it's very important to understand the contract between yourself and the backend too.

Right?

Like, you know.

Right.

We currently, like, you know, when I started iOS, we were doing,
you know Pless, which are xml, we were learning how to XML parse.

Right.

And, and then, you know, I think, don't remind me uh, JSON came along and know the horror stories, right?

Yeah.

JSON came along and now we have the json, you know decoding and encoding protocols.

Yeah.

We have the, the, you know, And as coder for binary phs, you know,
storing them, bringing 'em back to life, re reinflating them if you will.

You know, it kind of reminds me of, of astronauts going to the moon, the way they would dehydrate
their food and they would use water to reinflate them, to make them into look a nice mm-hmm.

Yeah.

Steak.

Exactly.

But , the, you know, so there's that.

And then, and now we've got the Code Codeable Pro protocol in, in swift to be able to handle that kind of stuff for us.

And yeah, you know, under the hood there's a lot going on, but, you know,
from a user point of view, it's, you know, pretty, pretty straightforward.

So, but I think, you know, understanding you know, looking at
like under learning about how, you know, basic http works, right?

Like how, you know, TLS works and encryption, you know, importance of encryption and importance of se.

It leads into the security discussion about, you know, making
sure that you're, you're talking to your, your backend correctly.

You're not, you know, exposing secrets.

You're not taking a user of password, for example, and passing around a plain text bad idea, you know?

You know, there's all kinds of different things that you can do there to, to sort of wreck somebody's day.

Right.

But by yeah.

I, I just, I shuder every time I hear one of these new, oh, so-and-so's been
exploited and so-and-so's, you know, change your passwords on this thing.

And, you know, it's getting old, just, it's just, it just scares the heck outta me.

Right.

Leo Dion (host): How do you think project management fits into this as far as.

Take a step back.

We, we talked about helping developers.

Mm-hmm.

learn, but like, as far as for if you're managing a team, like what do you think is the role of a project manager?

What do you.

They're, they're missing out

Tim Mitra (guest): on.

Yeah, it kind of de, it depends on the, depends on the company as well.

Like cuz the different def definitions, like larger companies, like a
bank would, would have like that broken down into four different roles.

Whereas a smaller startup might have it like all compacted into one.

But I, I know of an engineer here in Toronto pretty successful.

Solo developer who use uses project management tools just to keep himself on the street and narrow.

And I've thought about doing that, like thought about using tools like Trello.

Like at Koca we use Trello for managing our projects, but also Jira.

I'm a big fan of Jira.

I mean, not a huge fan of mean, it's the tool you use.

I know a friend of mine who's on monday.com who's shaking his fist at the screen right now.

But you know, it's just a matter it, I think.

It allows you to take, and it's part of, sort of agile flow that you want to basically take.

My agile joke by the way, is how do you, how do you eat an elephant?

You know, one bite at a time, right?

So you so basically take any large complex job and you break it down into smaller chunks.

Right.

And I think that's what Agile does, right?

And, and if you're using a tool like using something like Confluence to document what the, what the, the ticket's about.

you know, take the, the actual tasks of what you're gonna put
together in terms of an app and break it down into those steps.

What do I need to do first?

What do I need to do second?

Yeah.

Is a dependency here and there.

So tools like Jira and Trello help you sort of organize all the pieces like
you were, I think you were mentioning about you know, Ulysses as an example.

I think my friend Tammy is a big fan of s Scribner for writing, right?

Mm-hmm.

writing stories, writing novels, writing, you know, Well, it's your short story or a long story.

Yeah.

Leo Dion (host): You, you have to break it down into pieces.

Tim Mitra (guest): It's way too overwhelming, but you need to gather all your bits
and pieces into like a sort of a treasure box and scrapbook them kind of thing.

And I think that's what I think it's.

,
Leo Dion (host): I think Ulysses calls a material sheet, right?

I think that's the term

Tim Mitra (guest): they use.

Yeah.

Yeah.

So, and Scribner has a sort of like a sort of sketch board kind of place where you kind, you collect all
the bits and pieces that are gonna make up your story, your story lines, your character developments mm-hmm.

and that kind of stuff.

Yeah.

But I think, I think a tank in those same sort of, kind of criteria.

I do the same thing in my artwork.

I, I break it down into, into what has to happen first, what, you know,
I need to gather the supplies I need to, you know, have the stuff.

To go in order to, to basically get the project from one place to another.

And I think that's the same thing's true with, with any kind of mobile
development or even websites is, is you need to break it down into small pieces.

Like and maybe this is something that a, a, a young new developer can think about is like, you
know, like for instance, I have a, an app on a store or like a tutorial on using Touch id, right?

So I wanna use Touch id, Hey Lou Leo, I wanna use Touch id right?

. Well, what do I need to do first?

Well, first of all, I need to have some sort of app that requires login, right?

Mm-hmm.

. And so then I have to create a login view, and then I have to create,
you know, then I have to be able to handle the username and the password.

And as I said before, you don't want to handle that on Plain Tech.

So now you need to figure out a way to obfuscate.

The input from the user.

And then you need to have a way to talk to, maybe you wanna store something in user defaults key chain.

Okay, that's fine.

Maybe I want to use key chain, so then I have to go and learn about key chain,
you know, and, and break down all the pieces that, that you need to do in order to

facilitate getting to the point where you can actually add touch ID to your screen.

Right?

Yeah.

You know, so and we should probably talk about yak shaving at some point too, but, The, you know, the idea is like you.

You have a complex task to do.

And one of the things we did early, early, early in the days was when we were writing our iOS stuff is,
you know, we weren't the experts on it cuz I don't don't think anybody was in the early days, right?

So one of my junior's jobs was to just scour the web for a solution that's already been written
and somebody already written something about this that already does this thing rather than.

trying to invent it yourself, right?

Like one of the things about security is don't try to invent your own security.

It's already been done.

It's already been proven.

There are best practices, you know, you should, you should probably check that out, right?

Rather than trying to do it yourself.

But yeah.

Leo Dion (host): Do you use.

. Yeah, so I, I pretty much, I think I mentioned this, I don't
know, but I use like a spreadsheet to keep track of my to-do list.

Mm-hmm.

, but when Right.

I've individual repos or projects and GitHub has this now GitLab has, has like their little Jira Yeah.

Trello thing, and then I'll put those individual tasks and then I'll organize
those into a Trello board of some sort for like projects, coding projects.

So to.

.
Tim Mitra (guest): Yeah.

I just wanna show you here on, on my phone.

I mean so, you know, like one, one of the things I do in, in, yeah.

So here, like for instance, I've started doing, using my, I dunno if you can get the clear shot of this.

Leo Dion (host): It's too bright.

I can't see it.

Too bright.

There

Tim Mitra (guest): we go.

How's that?

There you go.

, right?

So you can see that, you know, I've got user stories and I'm using the notes featured to make little check boxes.

And this is just a simple, I broke this, you know, in terms of what I
want to refactor in the app is I broke down what it is I want to do.

And just using the notes app, I mean like you don't need to have Jira or Trello to start, you know,
like you said, you can use a spreadsheet, you can use a Symboled note, note taking app, right?

Piece of paper, right, right back of an envelope, literal.

.
Leo Dion (host): Right, right.

Well, and there's something nice about that, cuz then you don't have this feeling of, oh, this is permanent.

I need to save this.

Cause if it's on paper, it's like, okay, I copied it over.

I'm done pro processing it.

Yeah, I can throw it away.

What?

Yeah.

One of the things you wrote down is domain driven design.

What?

Yeah.

What did you mean

Tim Mitra (guest): by that, Tim?

So, so this is, this is something, it's interesting.

It, it came out of our work at Spot Hero, our, our previous cto.

I think he introduced the idea.

I'm not sure if, well, apologies to people at Spot Hero, so it wasn't his idea.

But there's a book by O'Reilly called din.

Domain driven design.

And the idea behind it is one of my favorite things about it is a thing called
event storm, where you look at the business logic of your, of your process, right?

And you kind of break it down.

You break down the, the using an event storm, you break down the
sort of processes that go into sorting out a a business thing.

Think of a bus.

What would you do?

Like maybe a pizza delivery service or something like that?

Right.

Okay.

You know, so you'd have different parts of your, of your organization.

One is, you know, there's gonna be an order taking system that's going to,
you know, describe all the orders, all the parts that make up a good pizza.

Right.

And then you've got your, your kitchen staff that are gonna
take the, get the orders, read what kind of pizza the person.

Somebody's gonna have to prepare the dough.

Somebody's gonna have to put all the, the, you know, the pepperoni and the cheese and the sauce on it.

Then there's the oven crew that's gonna have to put it in the oven.

Turn the heat, obviously heat the oven up, right?

Put the pizza in the oven to make the pizza.

There's gonna be the team that, after the pizza's been made, puts it in the box
and hands it to the driver, you know, with the order number on it, for example.

Then there's gonna be a cleanup.

Crew has to go in and clean the plates and clean.

Utensils that were used to make the dough and to make the pizza.

And then you're gonna hand it to a driver who's gonna go and, you know, put it in his car and take it to an address.

Well, where, how does he get to that address?

We need now we need, you know, an iPhone with a maps app on it to tell him where to go to deliver.

And then he gets the door, he takes a picture of the image and he,
so anyway, there's a whole complex thing to just making a pizza.

Right, right.

Or making a pizza app if you want.

Or making a pizza business.

Right.

So, What you do is you in, in the sort of the vein driven de development
is you say, okay, let's look at the making of the, the, the bakers, right?

The people that are actually putting the pizza together.

Right.

That's a domain.

Right?

And so you look at, we, we sit down and we examine all of the
pieces, all of the processes that go into making pizza, right?

Making the physical pizza itself, right?

Irrespective of all those other domains that I described, right?

And you look at that one particular domain and you go through all the sort.

Piece the, the, the, the sequences of, of events that need to happen in order to make a pizza.

And then we look at, well, who is the person who's gonna act on that particular thing?

Is it an automated process or is it an actual human being who needs to do this?

You know, like, can we write out, can we write up some coat that'll chop pepperoni?

I don't think so.

We need to have somebody with a knife to cut the pepperoni.

Right?

For example, I'm using a bricks and mortar kind of example for, for the sake of science, but yeah.

. So the idea is you, you kind of go through and you examine all of the sort of things that,
things, you know, traditional, maybe you have some, some traditional things you've been doing.

So, so far, and this is the only way we can get this to work, we use the, you
know, we use a piece of paper and a pencil because that's what we have, right?

Well, maybe we could use a piece, you know, a notes app or we
can use any spreadsheet or we can use something that's search.

, you know, like maybe down the road we might want to, you know, keep track of the orders and go back and see.

Historically, like when it comes to ordering the supplies, how do we know which are the most commonly
used pizzas or com most commonly used supplies, which do we have more, need to have more of or less of?

Right?

So by examining the sort of domain around what is needs to get done within that particular
sphere of, of the work, you can create a design like a, I mean a design in terms of.

The process of development.

You can write the little APIs, you can assign this, you know, create the assignments to people.

You can create user stories to facilitate, you know, the, that thing.

So if you think about, like, so take this back a step.

If this was, Hey, I want to write an iOS app that for ordering pizza, I.

Right now you have by examining the different, like by looking at this one particular
domain, we know what is required in that particular domain of the business, right?

And then we can look, we can go and look at, you know, the, the order takers domain.

We can look at the guy drive in the car domain.

We can look at the guy ordering the supplies to make the pizza.

That's another domain that can be, can be examined.

So you look at, you break down your business into.

Different parts and you put it together, you create a plan to put it together and it's great looking.

Come, yeah, go ahead.

Well, I'm,

Leo Dion (host): what I'm hearing is a great opportunity to mo modularize your code.

Cause like just listening to your pizza analogy, I'm like, each domain has its own library attached to it.

Right.

And like, like or each

Tim Mitra (guest): switch it might be a package.

Package, yeah, exactly.

, right.

Leo Dion (host): And it's all testing within its own.

Its.

set, whatever its own domain.

Yeah, yeah.

Right.

Yeah.

As opposed to, because I, I know I've done this accidentally, and by that I mean like, I know it's, it's, it's
naturally how you kind of factor things out is like the, the making the pizza does not care about delivering the pizza.

It only cares about making the pizza

Tim Mitra (guest): and Well, that's not true.

That's not true.

Well, you know what I mean?

When you, when you do your examination, you might have the drivers come and
tell you, well, you know, Leo, the pizzas are hot when they come outta the oven.

Yeah, okay.

I need a way to handle that.

Right.

So like there, yeah.

So it's, it does help to have cross domain or what we're talking, I understand where
the connection, multidisciplinary development, it pays to have those guys in the

room to have their sort of, because maybe there's a, maybe there's a way of doing it.

And, and if I can go back to the act shaving for a sec.

So do you, you, do you know the story about the ACT shaving, how that comes to being.

I think

Leo Dion (host): I've heard of it before, but I'll

Tim Mitra (guest): let you go ahead and repeat it.

Yeah, so, so it's one of my favorite things about like, when you're developing or thinking
about a, an app, an app idea, and it's all, it's kind of like, don't reinvent the wheel, right?

Mm-hmm.

, or, or you, you know, the ney, you ain't gonna need that kind of thing, right?

Yeah.

Right.

The idea.

Yeah.

The idea is I want to get, I want to get Leo a gift, right?

And, and I know Leo likes, you know, he likes warm clothing cuz he lives
in the northern climate and so he, I'm gonna make him a, a yak wool.

right?

Well, in order to make a yak, woo, it's kinda like a piece of story
I just told, but to make a yak wool sweater, I need to have some y.

, right?

I also need to learn how to knit, right?

So to make a sweater for, for Leo kind of thing.

So, you know, first of all, so I gotta go and learn how to make, how to knit and develop that skill.

But in the meantime, I need to get this Yaqui.

Well, how do I get the Yaqui?

Well, I need to go to the store that makes the get, that supplies the Yaqui.

Well, maybe there isn't a store that makes the Yaqui.

Maybe I need to figure out how to make the Yaqui myself.

Well, then I have to go and explore how to make wool.

right?

Mm-hmm.

, and then mm-hmm.

, you know, how to, how to spin it, how to turn it into yarn, how to, you know, to make the sort of,
and put it onto a spool so then I can, you know, knit it with my needing and needles kind of thing.

Right.

Well, you know, okay, so, but where do I get the supplies for the wool?

Like the raw fiber that makes the wool right.

While I need to go and get that from a yack, right?

Well, so then, but then I, in order to get the, convert the yack into the yarn, I need to figure out how to shave the.

, right.

And then, well, I don't have a yak here in Toronto and maybe,
I don't think you have one in Lansing, Michigan either, maybe.

No.

So we might have to go to a zoo or might have to go to like, you know, might have to go to Tibet or something.

I don't just, I dunno, sorry.

Tibet, if you don't have yaks, but you have to go to Tibet and figure out how to get a yak and grow it and feed
it and, you know, make it happy and keep it well enough that it'll keep you in supply of, of yak wall or yak fur.

Right?

Right.

And so the idea is like, you know, rather than thinking I need you, Find, you know, find someone
who already knows how to do the act, will make the act, will get them to come and do it for you.

Or like, you know, don't look, look, look for swift packages.

Look for cocoa pods that do the p the part of the app that you don't need to do the heavy lifting on.

I mentioned before, don't try and write your own security, write stack?

You wanna basically use a known security stack to, to do key chain is one example of a, of a security stack, right?

Right.

I'm waiting for Apple to come and fix security for us.

, you know, but yeah, that, that, I think that that that the act,
the Apple story's an old computer fable about or parable about.

Yeah.

You know, not trying to build it yourself, right?

Leo Dion (host): Yeah.

Yeah.

Exactly.

It was funny cuz before the recording we were talking about that Facebook article.

Yeah.

And like, if you read that article, it's like, , they built everything themselves and they, yeah, it's, they
try to, it tries to come across as victorious, but it doesn't sound sound like that's necessarily the case.

So yeah.

Yeah.

I totally agree.

Cool.

So before we close out, I wanted to talk about Apple rumors and history.

Mm.

Because we've, , we've been hearing a lot of rumors about a new, new piece of hardware, which, let me see.

Well,

Tim Mitra (guest): we, we always, I want to correct you and say we,
every year we hear about a new piece of hardware that's coming, right?

Yeah, that's true.

We're still waiting for the, the 16 gigabyte white apple car, right?

Yeah,

Leo Dion (host): that's right.

That's right.

This might, so this might be out if it, if it's out after it's been announced, which is mm-hmm.

is a possibility.

We won't have to cut this part, but we'll see.

Tim Mitra (guest): so it won't be out.

It won't be out in March.

Trust me.

You

Leo Dion (host): don't think so?

No, I don't think so.

You don't think it's gonna be the March event thing?

Okay.

Tim Mitra (guest): No.

It sounds like a WW d c thing.

I was listening to Jim, Jim Del Rumpel and Dave Mark talk about it on their show the other day.

I think that was a good call.

It's probably gonna be a WW C thing and the whole over.

I was talking to Daniel Steinberg on, on na on about it.

It's, it sound, I, it's probably gonna be like the central theme of Wwc wwdc, right?

This year it's gonna be all about this, this device we're talking about.

Right?

Leo Dion (host): We're all gonna be using reality kit.

Yeah.

So I don't Did you listen to ATP at all?

Tim Mitra (guest): I didn't, no, I didn't.

I, I listened to it a couple of weeks ago when they talked about M one
s, but I haven't listened or Mastodon, but I haven't listened since.

Leo Dion (host): Okay.

Okay.

Yeah, I mean, they, they did a pretty good job.

talking about how rumors and new platforms typically go.

Mm-hmm.

and the story with the iPad, the story with the Apple Watch, and
like how it was rumored and what the market was at that time.

I thought they did a, did a great job.

Mm-hmm.

Kind of talking about how these XR glasses are gonna fit into it.

Pro reality, reality pro deluxe max.com.

, but like Ultra.

You've got Ultra.

Ultra, yeah.

Sorry, I forgot about the new one.

Ultra.

They still haven't done Deluxe.

I'm waiting for deluxe.

Tim Mitra (guest): Looking forward to that.

I don't think Apple does Deluxe.

They don't do Deluxe.

Leo Dion (host): Okay.

No, no, not yet.

Never say never.

Right.

Yeah.

. So we, yeah.

I mean, it seems to, we, we talked about this on, on more than just code.

Yeah.

But my big whole thing was like, I don't see the market for it, especially where Apple is at.

Yeah.

Especially with games and bus business being the two.

, they want to do Microsoft teams with VR or they want to do games with vr.

Mm-hmm.

Right.

Apple's not very good at either of those markets and it's kind of
troubling trying to figure out where they're trying to position this.

Well, yeah.

What do, what's kind of your thoughts on, well,

Tim Mitra (guest): I want to take part a couple of things you said there, right?

What one thing about Apple not being very good at any, you an insert thing here, right?

Yeah.

And we talked about this on more than just code many, many times, but I honestly believe Apple leads from behind, right?

Apple.

If you think about it, think about it for a minute, right?

Apple has done some amazing things.

They've, they've turned the world on its ear with the iPhone, the iPod, you know, all kinds of different things.

But Apple, generally speaking, Innovate.

I mean, they innovate, but they didn't innovate the idea of something every single time.

Right?

They're never the first.

Leo Dion (host): They're never

Tim Mitra (guest): the first.

They're never the first, but they're generally one, one of the best, if not the best.

Right.

Because they take the time to look at something.

work out all the sort of kinks that they can see.

I mean, there's obviously, there's always loose ends and there's always kinks and there's always gonna be
like, you know, 10% or 20% of society's not gonna be happy with what they've done, but, or think it's too

Leo Dion (host): expensive.

Tim Mitra (guest): But, yeah.

Well, yeah.

Given, given it's too expensive, you know, he said the guy with the ultra watch on, right.

But you, but but.

, you know yeah.

You, you, they, they, they take an idea and they, you know, and
it's been this like, you know, from the Apple two computer, right?

Was something that Steve Wazniak saw in home brew and saw in the world.

He didn't invent the, the portable computer, but he invented the portable computer, right?

And then you got the Mac.

Well, the Mac was not it was innovative as a package and it was innovative from
a concept of the bicycle for the mind, but it was all Xerox park's work, right?

So it was, so it was Windows, windows, the menu and all that kind of stuff.

All that desktop metaphor.

That was all.

That all came from Xerox Park, right?

Then you get into iPod.

Well, iPod was a reaction to all the MP3 players that were out there that, you know,
Tearing up the market back in, in like, was that the nineties, early nineties, mid nineties?

Mm.

Leo Dion (host): No, not even.

I would say early aughts.

Tim Mitra (guest): Yes.

Oh, 2000.

So, I mean, so, so they, so Apple didn't invent.

MP3 players, but they, they entered the iPod, which was sort of their take on a better, a better MP3 player.

Right.

And then they, they, the little nanos and the shuffles, they,
that was to sort of squash all the other MP3 players out there.

So that was cool.

Right.

And then that went along great and, and iPod was doing pretty cool.

And it wasn't until they bought another piece of software, I'm trying to remember the name of havoc.

Snap NP or something like that.

I forget what it was, but it actually, it actually was an app that ran on your Mac sound.

I've, I've got it behind me.

I'm just, so, I'm just, you're talking about iTunes?

No, well, it became iTunes.

Right, right, right.

That's what I meant.

Yeah.

Yeah.

So they bought, they acquired this company that had built this software
that let you rip your C, your C your CD music into, into MP3s, right?

Mm-hmm.

. Okay.

And then feed them onto your thing.

So they, so iTunes became a way to create.

MP3s that you can put on and man eventually manage your, your iPods.

And it wasn't until Apple rolled that iTunes out onto Windows that the iPod really took off.

Yes, yes.

Right.

Because we talked about the other day that, you know, 5% of the market
is Apple, the rest is Windows, or most of his windows, 85% is Windows.

Right.

So that's mm-hmm.

, so that's mm-hmm.

a huge market.

It's kinda like I was talking about China earlier, right?

Yeah, yeah.

Yeah.

. So that was what put the iPod on the map.

Now all of a sudden everybody had an iPad.

It didn't matter.

Or sorry, iPod.

iPod.

Correct.

You correct me.

Yeah.

Everybody had an iPod, you know.

And and that sort of, you know, and then the next thing next, I remember driving to McElroy.

I was told this story a thousand times with my wife to down to San
Francisco, and she says like, what do you think the new thing is gonna be?

And I think, well, I've been hearing rumors of a phone, but I have no idea what Apple's gonna do with a cell phone.

Like, why bother?

They're making a cell phone.

Right.

And then it turned out well.

Okay.

It's not just a cell phone, it's a phone, it's an HomePod, it's, you know, or it's an iPod.

And it's an iPod and it's an internet device, right.

As as the famous, the classic, the

Leo Dion (host): classic three

Tim Mitra (guest): things.

Yes.

Yeah, the three things.

One more.

Yeah, one more thing.

And there's three things and one more thing, but you know, so that, that became the, that sort of tipped apple on it.

I mean, so as you go through every sort of thing that, think about anything that apple's
done other than Apple silicone, well, apple silicone was kind of like AMD's technology.

Is it AMD that makes the, the arm.

Arm, sorry, arm.

That's what I'm thinking of.

Thank you Arm.

Mm-hmm.

, it's arm technology.

Right?

And, and even the multi-touch device that we have on our iPhones
and our iPads, that was invented by somebody else as well, right?

Yeah.

So Apple's good at putting together a synergy of, of.

Ideas in such a way that it makes sense to the majority of people.

It improves the quality of their life, which is why people buy apple, mu apple stuff.

They don't buy the gigahertz, they don't buy the megawatts, you know, they buy very much.

So yeah, this makes me feel good, right?

Yeah.

And, and Apple cares about me feeling good and looking good with
my ultra watch on my wrist, which just looks really sexy, right?

It does look good.

,
Leo Dion (host): I just upgraded speaking with, I just upgraded to a series seven from a series.

Six, I think.

Yeah.

And the watch size, I'm just like, oh my gosh, I can't, because I went from 40 to 45.

Oh, the smaller size to the bigger one.

Yeah.

Yeah.

And I'm like, I couldn't even imagine going into an ultra.

So

Tim Mitra (guest): it's actually not that much bigger.

It's thicker.

It's heavier, right.

It's, I mean, it's thicker this way than, but, and it is.

It is.

It is.

It took a while for my wrist to get used to it, but physically, like size-wise,
what I love about this is, for me, I'm almost nervous about cracking the edge of.

my phone on the, on a brick as I walk through a doorway.

Right.

Well this has got like a titan, titanium ridge all over.

That's one of my watches.

Yeah.

And for me, the big, the big selling point for me is the one button to get activities going.

Oh, you know, nice.

The activity button where I think it's called that.

Leo Dion (host): Yeah, yeah, yeah.

No, I know exactly what you mean.

I'm

Tim Mitra (guest): not a huge, I'm, to be honest with you, I wear a watch every day, but, but watch is not my thing.

I mean, the watch os was a real disappointment.

Watch os 1.0 was a real disappointment.

Right.

Yeah.

Leo Dion (host): Going back, talking about the headset, like okay, like the, the

Tim Mitra (guest): one thing that, so we're talking about VR goggles.

I don't think we've actually said that to people.

We're talking about the VR sort of a reality.

Reality vr, that's what we be called vr, just wanna be clear with people.

. Leo Dion (host): So one of the points I made on ATP was that like, and we're talking about these guys

Tim Mitra (guest): here, the a augmented reality device.

Leo Dion (host): Exactly.

They look exactly like that.

Tim Mitra (guest): Yeah.

It's gonna be exactly this.

Yeah.

The

Leo Dion (host): one thing they said was like, multitouch was a big killer feature of the iPhone.

Yeah.

That made it more like, okay, now I see why this is such a

Tim Mitra (guest): big deal.

Also, the biggest downfall, cuz, I mean, have you ever tried to type on an.

?

Yeah.

Why ? Well, cuz I mean, like, why did they have to make a, a keyboard for it if it was so good?

, like, I have Right.

You know, I have the magic keyboard here and I

Leo Dion (host): love it.

Well, I miss that.

I mean, I miss tactile.

I mean, there is benefits to how Blackberry did it, but it Yeah.

Tim Mitra (guest): In any case, I don't know.

It's good and bad.

I mean, I, I, you know, I right.

Yeah.

Well,

Leo Dion (host): and, but I think that's the thing is like the.

, even with multitouch and losing a physical keyboard, like they way
overcame with the snappiness and, and the great, the, the great ux.

Lately the auto,

Tim Mitra (guest): you see that is awful.

What's that said lately?

The autocorrect is awful.

Like it's just, it's just lost its mind.

I wish it was a way to reset your, your library of auto, of your auto complete nonsense,

Leo Dion (host): right?

Yeah.

Yes.

Exactly.

Exactly.

But like even with like the dynamic island, like.

I didn't buy a new iPhone, but it's like impressive how apple's like, oh, you did okay.

But you're like, you saw that presentation.

You're like, oh, apple always comes up with some clever workaround for some physical.

Tim Mitra (guest): Well, can I tell you about some of the problems with the dynamic island?

Leo Dion (host): Not, not yet.

I wanna, I want to go back to the headset.

I wanna go back to the headset.

But

Tim Mitra (guest): like my recommendations, don't buy more than one headset, 1.0.

.
Leo Dion (host): Yeah, right.

We'll, going back to the Apple Watch or the home phone.

Well,

Tim Mitra (guest): no, not so much that.

Yeah.

It comes back to, we'll get to my point in a minute.

Sorry.

Continue.

Leo Dion (host): But like, do you think that there, what, what could possibly
be like a killer feature that would make these more substantial that than like

Then the current sets of VR headsets mean because like I had, I had
like, I had this Windows Mobile smartphone before the iPhone came out.

And like my Windows Mobile, I'm not talking the one that was actually half decent looking.

I'm talking like basically was Windows 98 on a phone?

It was garbage.

You had to have I remember those.

Yeah.

And then people who are like, oh, how are they gonna make the iPhone any better than this?

And then they like totally.

And like to me, like that's, that's the only thing I could see is like, they have something that is going to be
like, we're gonna look back and be like, oh my gosh, the ocul Oculus is so old and like, it's so janky and like Apple

Tim Mitra (guest): totally new.

It doesn't even come in titanium.

Exactly.

Yeah.

Leo Dion (host): with the, with the orange button on the side, right?

Yeah.

What could be the thing that like, like Apple could do with these that's, it's gonna be.

Oh, that's it.

Now I, Andrew, get it.

Like, what could I, I can't even think of it.

.
Tim Mitra (guest): Well, I mean, we talked about that the other day too, is, is the watch.

You know, initially the watch was not a fitness device, but it is a fitness device.

I mean, it's totally like I bought, I bought the four because of the EKG again, when I talked about the gray hair.

Right.

You know, the EKGs important to me, right?

Yeah.

Yeah.

Blood is an important thing.

Not so much to me, but like the last couple of years, people getting covid blood was a huge thing.

Right, right.

Blood oxygen levels, but, or, you know I, I'm not a lady so I really
can't speak to cycle tracking, but I'm sure that's an important thing.

Right.

I mean, I've, I've tried to get, I've tried to get my wife pregnant and
that was a chore, you know, with, with thermometers and log books and yeah.

I mean, please solve that problem for me.

Apple, thank you very much.

Right, ? I think, I think that you.

Again, I think we also agreed to agree that we are not the target market for this product.

You and I, but but I, I don't know, like, I think I, I riffed on the idea of, of maybe, you know, heads up navigation.

You know, golf maybe tells you how far the hole is from your, from your putt, right?

Or your, or your shot.

Maybe it's used, you know, can be used in, in industry where, you know, like warehouse management or, I think
I, I remember seeing an early I ar example back in the early days of the iPhone where you held up your camera.

I think it was like Yelp, right?

And it showed like you could hold it up and move it around like this and it would show you like,
okay, there's a pizza restaurant over there and there's an Italian restaurant over there and yeah.

Yeah.

And as you sort of, it sort of figured out where you were pointing based
on the G P s, what was in front of you, maybe that's something to do.

Heads up.

, maybe it's heads, maybe it's like hey, you know, you're reading your
text messages, there's a telephone pole you're walking into, right?

Like, like maybe it's, maybe it's heads up navigation for pedestrians or bike rider.

Maybe you're riding a bike and it gives you like a heads up display, right?

That's true.

Or maybe, yeah, I mean, or like in the gaming thing, maybe you can play like Red Dead redemption as if you're.

The actual environment of that world.

I mean, I dunno if you've ever seen the world, but it's huge.

Like, it goes on, like, you know, it takes you 20 minutes to go from one town to the other, riding a horse.

I mean, it literally, like, it does that, you know?

Yeah.

So, I mean, from a gaming point of view, I think there's, there's, there's opportunities there.

Heads up.

I mean, like maybe a doctor could be wearing it and just sort of like, look at you and maybe he put some sensors on you
and he can just look at you and see that your heart's like, properly working or, or your blood ox is not good or Right.

I mean, I'm thinking, I can think of any number of ways that, that AR and VR could be used.

I mean, I, I think, joked with you about the fact that people were having relations.

Using VR back in the early days.

Right, right, right, right.

Devices that you could, wearable devices that would stimulate whatever.

Yeah.

Yeah.

I mean, so, so where, I mean, architectural engineering, I can think
of tons of different ways that, that it'll, it'll improve things.

I mean, I don't know whether it'll take a long time before the law
lets us do it, but maybe you wear the headset when you're driving.

Right, right.

Maybe, maybe it puts your speed in your, and, you know, things right in front of me.

My concern about it is like the whole.

and like I was telling you about my, my, my nephew's place, they had to move all the furniture
out of the way when they had the Oculus on because you're gonna hurt yourself, right?

Yeah.

My concern is when

Leo Dion (host): you're out, but then you have crash detection on your Apple Watch.

So, but that's

Tim Mitra (guest): after the fact.

You, it's too, I think it's already too late to prevent the accident if you've already had it.

Right.

, you know, or, but, but, but then again, like we also talked about, you know, may, maybe it's an experiential thing,
maybe you know, Trevor Noah at the, at the Grammy Award is wearing a Grammy's just happened this weekend, but he's

wearing a headset that lets you go and have a conversation with Beyonce as if you're in the room with Beyonce.

Right.

Right.

Maybe it, maybe it's concerts like now, instead of going to a physical concert to see a band
play, you know, you can actually experience that through a VR like you put on the headset.

Now you're in, you know, you're in the stadium, you're, you know, with all the other.

Avatars, you know all the emojis in the audience, right?

Yeah, yeah.

Instead of having audience members, it'll be all emojis.

You right Mark is wrong about importance of emojis, but you know,
maybe that may, maybe we all, maybe we all attend WWE Z this way.

Maybe they're gonna have a developer kit and they'll ship.

That would make total

Leo Dion (host): sense as if they do that.

Yeah.

Like especially if you think they're gonna announce it in June that.

That would,

Tim Mitra (guest): well, I mean, I mean, June, I can tell you
from, I mean as you know, I, I've done some work for Apple.

I can tell you that leading up to WW wwc is the big, I mean, Phil Schiller talked about this.

This is the big pin.

That's their Christmas, that's their, everything leads up to wwc.

Right?

Yeah.

You know, that's when all the stuff gets

Leo Dion (host): out.

We'll see.

Yeah.

We'll see.

Tim, thank you so much for coming on the show.

Where can people find you?

Tim Mitra (guest): I'm generally on Twitter and Mastodon as timmitra, Tim
Mitra is my name, and that's how I, you can find me on the Twitter machine.

You can listen to me on more than just Code podcast mt.

jc.fm.

I'm on Podcast.

Podcast.

And that's podcast.com.

As well you can find me on LinkedIn if you'll, you know, look for me IT Guy Canada.

And yeah, those are pretty much the places to find me that, that I hang out.

I also hang out on a few Slack channels, some of, some of the iOS folks, slack channels.

We have a Slack channel for our own podcast as well.

And I also work with the folks over at Kodaco, so one of the technical letters and sometimes writer over there.

So you can find me on the Ray Wenderlich Kodeco forums.

Leo Dion (host): Thank you so much, friend Tim, for coming on the show.

I really appreciate it.

Thanks for having me.

If people wanna find me online, I'm at Leo g Dion.

My company is BrightDigit.

Take some time to like and subscribe.

If you're watching this on YouTube, this is a podcast, please.

Put it, review and I look forward to talking to you again in a couple of weeks.

Thanks for joining us.

Bye everyone.

Creators and Guests

Leo Dion
Host
Leo Dion
Swift developer for Apple devices and more; Founder of BrightDigit; husband and father of 6 adorable kids
@TimMitra@mastedon.social πŸ’‰x4 β€οΈπŸ‡ΊπŸ‡¦
Guest
@TimMitra@mastedon.social πŸ’‰x4 β€οΈπŸ‡ΊπŸ‡¦
Host of MTJC Podcast & Spockcast. Artist, iOS SME, Sr.EM, evangelist, tech journalist, trainer, maker, speaker, Feminist, πŸ‡¨πŸ‡¦ vexillographer, views are my own.

Join our newsletter

checkmark Got it. You're on the list!
image of podcast supporter
Join 1 supporters
Mastodon Β© Bright Digit, LLC 2018