July 21, 2022 • 48 mins
It’s time to talk about sharing your Podio data outside of Podio…and in this awesome episode we welcome back returning champion Pete Cuff from Future Solutions.
This is a great episode, as we always talk about the power of Podio….but what happens when you want to take that data and share it with outsiders (contractors, customers…you name it).
In this episode Pete and Jordan talk about some of the ways you can share your Podio data with outsiders, and particularly focus on the pros and cons of each method.
If you have data in Podio you want to share with anyone outside of your Podio system – this is the option for you (also check out Jordan’s recent masterclass on this subject where you can see some examples on your screen).
Show Links:
Check out Pete’s amazing Podio consultancy at https://futuresolutionsonline.co.uk/
Have you checked out our Podio Masterclass (https://www.wearegamechangers.com/category/podio-masterclass/)? Make sure to subscribe to our YouTube Channel (https://www.youtube.com/c/JordanFlemingGamechangers) to get notified of new videos.
Please don’t forget to leave us a review and subscribe to the Podcast and if you’d like to be a guest on an upcoming show please register your interest at https://bit.ly/supercharged-guest
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Narrator (00:00):
Welcome to the supercharged with Jordan Samuel
Fleming, your weekly podcastdedicated to what your business
can achieve when it's powered byPodio. Join us each week as we
learn from the top Podiopartners in the world as we
investigate system integrationsand add ons and hear from real
business owners who haveimplemented Podio into their
(00:21):
business. Now join Jordan SamuelFleming, CEO of smartphone for
this week's episode.
Jordan Fleming (00:28):
Hey, everybody, and welcome to this week's
episode of supercharged I'm yourhost, Jordan, Samuel Fleming,
here to talk all about the powerof workflow and automation, when
your business is powered byPodio. Well, this episode, this
week's episode brings backanother returning champion for a
very specific reason. I broughtback Pete cough from future
(00:50):
solutions. A Podio partner, justlike I used to be does a lot of
building inside of Podio. Andwe're here to talk about a very
specific thing that we get askedabout all the time, which is how
do I share Podio data withpeople outside of Podio? What
are the best practices and Peteand I dive into this a little,
it kind of goes along with amasterclass that I'm putting up
(01:11):
right now. It's showing you thisin a more direct way. But what
are the ways you can share data?
What are the pros of each way ofdoing so? What are the cons?
What are the best practices?
What are the options you haveavailable to you? You know, we
all know, and certainly if youlisten to this podcast,
hopefully, you'll hear mypassion about how amazing Podio
is to manage the business, dothe workflow, you know, share
(01:37):
information across your team.
But what about those times whenI need to show a customer
something I need to bring acontractor in and show them
something Podio is built forthat in many ways. And we go
through in this podcast, thekind of different opportunities
you have, and the pros and consaround them. As always, please
do make sure you head over theYouTube channel, give us
(01:59):
subscribe, make sure you're upto date on the masterclasses, go
to your podcast platform, giveit a like and a share, give it a
rating, it really does help tospread the gospel of Podio. And,
of course, as always enjoy thisepisode, very special episode
talking about how to share Podiodata outside of Podio. With Pete
cuff, let's have a listen.
(02:28):
So we decided that for thisepisode, we would focus on kind
of deep diving into sharingPodio data, right? Like, you
know, and for those who I shouldprobably start out with today's
guest, as you've heard from theintroduction is Pete cut from
future solutions. And pizza,very old, old old photo partner,
(02:57):
his company future solutions,build systems support systems.
And when we were chatting about,you know, things that we thought
would be useful for the podcast,we always try and make sure we
come up with ideas that will beuseful. We talked about this
notion of sharing Podio datawith other people. And that's
really where we want to kind offocus on today and discuss the
(03:21):
different ways you canachievement. And also kind of
pros and cons about it. Right?
Yeah, so
Pete Cuff (03:27):
one of the one of the kind of great things about Podio
is when you're in it, it allmakes sense. But when you're
when you're out of it, or you'rejust starting to get into the
first time, it can be veryconfusing, very overwhelming.
And, you know, first andforemost, Podio is a
collaboration platform, it'smeant to bring people together
into one place, but sometimesthat place can be a bit too big
(03:50):
or too you know, you don't wantto share 100% of everything, you
just want to share 1% of whatyou want that one person to see.
So that's when these differentkinds of methods can come in
handy.
Jordan Fleming (04:01):
That and I think you know, because so many of us
build, you know, Podio becomesusually a real powerhouse of
your business, right like it, itends up kind of touching and
bringing in so much of your dayto day kind of business that you
(04:23):
end up having a lot of data inthere that you may want to share
with someone outside of yourorganisation, an accountant or a
consultant or contractors orwhatever that is customers. And
because Podio is so powerful atthat part. The next logical step
is how do I externalise some ofthe amazing things I've done in
(04:46):
my Podio How do I get theresults are the information into
someone else's hands? So it'sit's not even just about you
know, about the somewhat kind ofconvoluted onboarding. It's all
So about, you may never wantpeople to know what Podio
exists, sometimes, and sometimesyou do want them to know Podio
exists, or sometimes you don'tcare that Podio exists. And each
(05:09):
use case has its value. So ifit's okay with you, Pete, I'm
going to drive the the firstpart of this to say, I want to
focus on this in two parts,that's using the word part way
too many times I understand. So,part one will be an, you know, I
want to focus on sharing Podiowith other people. And part two
(05:34):
will be sharing Podio data usingan external vehicle of some
sort. Because there are amultiple different ways of using
Podio. And sharing things withthe native Podio kind of
structure. And there are plusesand minuses all of them. So if I
think about a Pete, I'm thinkingof, you can share an item, you
(05:58):
can bring people into Podio intoa workspace, and you can use a
native webform. Those would bethe three that I would class as
part one, right? That is you'reusing Podio. And you are
exposing people to Podio in a ina certain way. So let's talk
about those first. Why do youthink you know, if we go through
(06:21):
those three, where are theygood? When are they bad? When
are they in between? What do youthink? Okay,
Pete Cuff (06:25):
well, let's start I suppose with probably the
easiest one, which is to sharean individual item, interact
with with somebody else. Sofirstly, the logistics of how
you actually do that istypically on say, the comments
field on the right hand side,you can just do an act symbol,
and then start typing insomebody's email address. And
(06:46):
that will start sharing when youthen send that message, you
write a comment to them, sendthem that message, they will
then receive an email from Podiowith Polios, branding, polios
name, etc, on it, saying, youknow, Jordan shared this with
you or Jordan said this to you.
And then it will have a, youknow, a snippet of what's going
on. And it will have a buttonsaying click here to reply or
(07:08):
click here to go and have alook. And that, in itself is
brilliant, because it putseverything that you need just
onto one email, everybody knowsand trusts email, it's very
familiar. And of course, it'sit's read only as well, at that
point, they can't they can'tchange anything, they can't do
(07:29):
anything with it. Now I'll kindof spare the details of once
they're in, you can change thosepermissions and so forth. But
what it will then do and driveis that that person, then in
order to see that item needs tocome and open a Podio account.
Jordan Fleming (07:46):
And that's where it all falls down. Yeah, that
Pete Cuff (07:49):
Citrix is model.
Yeah, that makes sense. Right?
Jordan Fleming (07:53):
I mean, it makes sense. But it is a massive
weakness of this type ofsharing. Because a it drives the
necessity of I gotta create anaccount for this shit. Like, you
know, so you know, there's thatproblem. And the second problem,
I think, because, you know, wecould spend 40 minutes just on
(08:14):
this bit, and other and nobodywill learn anything. The second
problem is, it's really a clunkyway of sharing information,
because there's no filtering, orsorting or organising that which
as you have shared with you. Sowhen that person even if I'm a
Podio user already, but I'm in adifferent company, if you share
(08:36):
me something an item, it goesinto my shared with you section.
And there's no filtering, nosorting, no searching. And so
beyond a handful of things, itbecomes a fucking pain in the
ass.
Pete Cuff (08:53):
I knew it wouldn't be long before various exclusive
left your mouth when it came onabout that process. Yeah, you're
right. It's really annoying,it's fantastic. If you've only
got one or two things that youwant to share with the person,
that's where it comes into itsown. That's great. And also it
works well. If you're able sayto talk to that person first.
And say by the way, you're goingto receive an email, it's from
(09:15):
our system Podio you'll need toopen an account, don't worry,
it's all free, follow this stuffon on screen and you'll be fine.
And as long as you can kind ofgive them that warning that this
stuff is about to happen, thenit can probably start to make
sense. I accidentally shared anitem with a friend recently
sorry, way back in the day. Andhe replied back saying So go on,
(09:35):
then what's this Podio thing andI had to kind of explain it's
this big old system. Sorry, Ididn't mean to do it. I couldn't
pull it back. And it was justlike well, it would have been a
lot easier. If it was he was onthe phone at the time that I did
it. I mean I said that checkyour inbox now you've got a link
Yeah, so that's that's thethat's the first one but yeah,
the downside is most definitelythat you go on to the Citrix is
(09:59):
Citrix is onboarding journey,which is clunky as hell, and
doesn't make sense, and they tryand explain what everything is,
when really, it's justpointless. Well,
Jordan Fleming (10:10):
there's that.
And then that leads us into whatI would class as the next step
up, which is sharing bringingsomeone into a workspace right?
Now that is a big step up inthat it can become a truly
collaborative tool with anexternal group of people, you
can very successfully and I havemyself and seen many of our
customers very successfullybring in external teams into
(10:33):
workspaces, and have them startto love Podio, you know, and
save them really get you going.
So this, this is a definite stepup in that what you're doing at
this stage is you're actuallybringing them into a workspace
or multiple workspaces, butusually just one. And you're
essentially when you do that,you're giving them the
(10:55):
opportunity to use theworkspace, the apps and
everything, see everything asthough you they normally would.
And that means that they cancollaborate with you, like any
Podio user can. But of course,as Pete, I'm sure we'll both
point out. The downside of thatis if you're bringing people in
(11:15):
who don't need to be in Podio,very often, you're essentially
going to be a Podio helpline forthem, because they're going to
come in every month to see theone thing you need them to see.
And they're going to be like,What the hell? Where do I go?
How do I you know, that thatwhole onboarding process when
you get a new staff into Podio,and the time it takes for them
to learn it? You have to do witheverything? Everybody over and
(11:36):
over again?
Pete Cuff (11:38):
Absolutely. And it's complicated, because it's
unusual. People aren't, youknow, people don't know how to
use Podio out of the box, youdon't know what workspaces,
yeah, the first time I loggedinto Podio, and took out an
account, I didn't get it. And Inearly closed my account and
walked the other way. I'm veryglad I came back a few years
later, and gave it another try.
And it finally started to makesense to me. But there's a huge
learning curve. And you eitherget it or you don't. And most
(12:00):
people don't, in my in myexperience, and the thing that
when you add someone into aworkspace, if you are getting
them in my my advice would bewhatever that workspace is, in
the first instance, make it assimple as possible. So for
example, one of our clients usedit as a way to have a forum for
their, for their customers. Andthey had several 1000 external
(12:22):
users in that in that workspace.
And yes, most of them didn'tengage with it, but some really
got it. And you know what it'slike when you go into a forum,
and you see, you know, the sameold names over and over and over
again, it's like it did, therewere people who got it, and
they, they just need to get to acertain point to make it work.
But it's a real challenge, Ithink, to get people to
(12:45):
understand it. And one of theways that you could seek to
improve that, as I've saidbefore, firstly, ideally have
someone on the phone or inperson and show them through it.
But for purposes of scale, whynot record your own onboarding
journey, why not record your ownvideo showing them this is the
workspace that you're going tobe a member of, or a sample of
(13:05):
it. This is what you click on,this is an ad, this is the
activity stream, etc, etc. Andthen you can really target your
message and get those users toonly see the stuff that you
really want them to focus on.
Jordan Fleming (13:18):
I agree with that. And the second thing I
would say about that is thatthis is really in my opinion,
this is really only applicablefor the people you want to be
working in Podio with on a veryregular basis. You know, it
doesn't really matter how simpleyou make the workspace, if
they're only going to see itonce a month, find us one of our
(13:39):
other methods we'll talk aboutbecause it's not worth the
hassle. But like if you've gotI've seen people bring customers
in very successfully to Podioand contractors, subcontractors
etc. And as long as you have a,a clear and an obvious workspace
with a very few set of apps thatmake complete sense. And they
(14:01):
people are working in there allthe time, it can be incredibly
powerful, because you suddenlyhave all the collaboration that
you're used to, but you've gotit with people who are outside
of your organisations, you gotsubcontractors who are managing
a project with you, and they cansee everything and comment and
assign tasks and do tasks. Andso there's huge value to that.
And I can't stress enough thefact that Podio is business
(14:23):
model is to its credit in thisway, you can bring an unlimited
amount of external users intoyour organisation and for free,
and that is not something thatmost of these systems have. And
that means that if you can getthis model working, you can
actually bring a lot of peopleinto your system, have them
(14:46):
fully working inside it, and youare not paying a monthly fee for
those people. So that's a hugebenefit to that model.
Pete Cuff (14:53):
Absolutely. Yeah. And I'd like it also a bit to say
Google's model which is youknow, you can You can attach a
Google doc to a email. But whatyou really want to do is open a
Google account. So you can nowcollaborate on that item life.
It's kind of that similar modelof if you can get them in and
explain to them what this is,then that you really start to
reap the benefits on the otherside.
Jordan Fleming (15:15):
100% 100% agree with that. And, you know, and
just to round out the internalkind of Podio bits, because I
don't, I want to get through allof these today, if we can.
There's one final one, which iskind of using the internal bits
of Podio, which are prepopulated web forms. So if we
think about it, the first one isthe one I never recommend, which
(15:37):
is simply to share an item. Itis the worst case, you know, in
my opinion, bringing people intothe workspace is the second one,
which can be hugely powerful,and has huge benefits, but has
to be done in a specific andcontrolled way. And then the
third one is the individualprefilled webform. So Pete, why
(15:58):
don't you tell us a bit aboutthat.
Pete Cuff (16:00):
Okay, so the prefilled webform, that's the
one where you're going to needthe most level of, I'd say
coding slash planning to makethis work for you. But that the
flip side of that is that it'svery, very powerful, if used
correctly. So every single appin Podio can be turned into a
webform in just a couple ofclicks. That means that external
(16:22):
users can populate the whicheverfields you set to be shown with
the data. So it's like they'rein Podio, and putting in the
data themselves. But it's alldone at arm's length outside of
Podio. Looking in. Now, how youpre populate fields on a
webform, because when it firstloads, it will be blank. How you
(16:45):
pre populate it is your pins, aquery string. So that's a set of
parameters and values to the endof the URL, the website address
for that, for that webform. Andit means you can do things like
let's say you've given eachcustomer or client of yours an
ID that you want them to cite ora code to put in to get a
(17:09):
discount or something like that,it means that you can pre
populate that field so that whenthey arrive, it's already there.
Now the details of how to dothat are documented more in the
Podio help documentation, Ithink I'd recommend working
through that in person ratherthan trying to explain it over a
podcast. But the basic premiseis you have the the URL of the
(17:32):
webform, a question mark, andthen you set like field X equals
ABC field y equals 123. And itwill populate.
Jordan Fleming (17:43):
Now hugely powerful this hugely powerful,
Pete Cuff (17:46):
because you can make it do really clever stuff,
especially when you then combineit with a little bit of styling,
so a little bit of HTML and CSSstyling. And that's basically
what makes the form look the waythat it does. So it comes with
forms out the box comes withlots of different styling
options that you can choose froma drop down. But then there is
an option also on that stylingbit to to add custom styling to
(18:08):
Custom CSS. And that's where youcan do things like hide a field.
So you could use your querystring up in your in your
address bar, to say that youwant to set the ID fields to
123. And then you can set yourCSS your styling to say and hide
field ID so that it's beingpopulated that they can't, the
(18:28):
person looking at the webform,when the filling in can't see
that the ID is alreadypopulated. And most importantly,
they can't remove the ID, theycan't hide that they can't
change it accidentally. So it'sreally powerful say to, you
could you could populate it withsomebody's first name and last
name so that they know thatthey're that you know, you've
(18:48):
got their data or you know thattheir name or their email or
whatever, but you might want tohide how you got to that point.
So
Jordan Fleming (18:56):
I'll give you a great example of real life
example, which shows just howthis little thing can can make
your system so easy. And that iswe build a system years ago for
a training company that like didoutdoor training and adventure
stuff. And so they would have,they would have a customer, they
(19:19):
would have people who registerfor their stuff for their
events. And then they will wantto maybe get dietary information
and sizing and whatever. And sowe simply used globey flow PW
Citrix PWA to create the URL bydropping in tokens, right by but
by dropping in. So I could getthe name from one app and the
(19:42):
event ID from another app. And Icould do all that because again,
you've got the power of CitrixPWA to grab information from all
over the place, create this URL,which meant that when they
clicked we got they got theautomated email that said, hey
Jordan, it's time for you toyour event. Just two weeks away,
it's time for you to give usyour fucking dietary
(20:03):
information. They clicked on thelink, and it populated and it's
like Jordan, the name is JordanFleming the event is, you know,
camping inactive, the dietaryrequests or beer, beer and
meats, and etc, etc, etc. And itwas all prefilled with the
information about the event andme. And then I could simply do
the bits that I needed, andupdate bits, like my contact
(20:27):
information and choose that. Andthen it went into Podio. And we
knew exactly what it was whatevent it was for, we got
everything in for there, theydidn't have to type in a bunch
of fields they are they didn'thave to do their name. Again,
they didn't. And moreimportantly, they didn't have to
do things where they could fuckup the results I needed. So like
an event ID or Person ID, youknow, when I needed to make sure
(20:48):
that this was going to registeras Jordan Fleming, I don't want
to put that in their hands. Andthat's one of the powerful
things about web, the webforming elements. The way Pete's
talking of is, if you reallytake it to the way it can be
done, you can take informationfrom all over your Podio system,
pre fill the bits in the form,and give someone a really guided
(21:12):
experience where all you need todo is gather a bit of data.
That's all you need. Okay, handsup who's using Podio for real
estate, and they don't want moreLeads. Nobody. You want more
Leads closed, well check outsmartphone for Podio, the only
phone system fully built forCitrix Podio. With an fully
integrated power dialer and ouramazing mobile apps, it means
(21:35):
wherever you are, you can makemore calls, love to Podio, send
more texts, love to Podio andclose more deals all log to your
Podio CRM, click the link, checkit
Pete Cuff (21:46):
out. But then that leads us simultaneously so
nicely on to the kind of con ofof this approach, which is that
web forms are just catch tools,they only receive information.
So whilst you might be able topre fill them for them, you are
still then receivinginformation, you're not updating
anything, it's creating a newitem. Yeah, it creates a brand
(22:09):
new item in the app populatedwith whatever they have
submitted on that form, whetherthat's prefilled or not. And
therefore that a importantconsideration, I want to think
about when using prefilled, orblank Web Forms is generally
speaking, it's best to justremember everything, there's a
catch, and therefore there couldbe duplicates. And if you are
(22:30):
wanting to update a record as aresult of receiving a webform,
you need to use either manual,but more preferably an automated
approach to check that the firstthing that you get through then
goes off and updates the masterrecord, wherever that may be
somewhere else. And just treatit all as like a big intro, and
(22:50):
then work out how to deal witheach one as it comes in.
Jordan Fleming (22:53):
Yeah, it is much better, as in my opinion, it is
much better as a way ofgathering information rather
than updating. So you can use itto like, hey, update your
contact details, you know, this,you can do that. But it's gonna
require you to create a new itemand then check and replace, or
whatever and, and there arebetter ways that we'll talk
(23:16):
about in a second to doing thatsort of thing. But where this
comes into its own are thingslike the use case I gave you
where, you know, I've got anevent I'm running, and I'm
trying to gather, you know,information from someone about
their next of kin and theirdietary, those are perfect,
because what you're really doingis you're using the prefilled
bits to identify the parts youneed to ident like this, it's
(23:39):
this person for this event onthis date, etc. And you pre fill
in that bit so that you theycan't touch it, and you're
gathering new information you'venever had. That's where this use
case fucking flies in myopinion.
Pete Cuff (23:52):
Yeah, absolutely agreed. Yeah, as I said,
Remember, it's a catching tool.
It's not an updating tool.
Jordan Fleming (23:58):
Yeah, absolutely. Now, a last one I'm
going to touch on although Ithink this will deserve its own,
I'm gonna do its own. I may getAndrew and maybe you on a group
one to talk about it. Because Iwant to dive in more into the
capabilities of a PWA ExternalLink. Because I don't want to
(24:18):
I'm not gonna dive too much intoit on this episode, because it's
a long fucking narrative that wecould drive it for a while. But
the last kind of internal thepodium, one, in my opinion, is
an external link. And it's thethis is the one that bridges the
gap between using just Podiotools and kind of externalising
them and using some of the othertools we're about to talk about
(24:39):
and an external link issomething that you can create in
globey flow in Citrix PWA. Andessentially, it creates a unique
link that can be clicked on. Andyou can actually make the page
it goes to do almost anything.
So you can display data, you candisplay tables, you can Get
referenced items from all overyour Podio create tables and
(25:01):
buttons, and links to new webforms, you can create it as a
holding page or as a sort of asplash page, which then links to
a bunch of things. It can beamazingly powerful. But it also
is slow. Very. So if you thewarning is it's great to use in
some circumstances. But if youpush it too far, and we've
(25:25):
pushed it too far, if they're onlike a 3g, 4g connection, it is
not a sensible option, would youagree
Pete Cuff (25:36):
completely. And in its most pure form, when you say
in PWA, I want to create a newexternal link for this for this
app for this item, the firstbrick that it automatically puts
in on on the flow is a web a webpage, brick. And what some
people don't realise is that asyou've just then said, whilst it
(25:57):
puts it in at the top, and thenyou can put more things
underneath, you can change thatorder. And put in your get
referenced, you can buildtables, you can build variables,
you can do whatever the hell youlike, and then show the web
form, sorry, not the web formthe web page. But that's the
problem is that whilst anythingthat you've put above the web
page is going on the web page isnot loading. So the person at
(26:20):
the other end is waiting for aprocess. So all they're seeing
is a blank white page, waitingfor the web page bid to be
triggered and come in. And soit's yeah, it should be used
carefully and infrequently wouldbe my steer,
Jordan Fleming (26:36):
I have a great success in using this in where
we've maybe sent an email. Andin that email, we've got an
action button. You know, do youwant to confirm that you love
cheese? Yes. So you know, andthey action button is yes. And
(26:58):
when they are now let's give areal example, a property
management example where thelease is up for renewal, and
we're going to send them a 90day notice that it's up for
renewal, is it your intention tostay another year, you know, and
click here to tell us you wantto stay another year, click here
to tell us who you don't. Andwhen they click here to say they
(27:19):
want to stay in the year, we'reusing a Podio. A CD is Citrix,
PWA, external length, which thenwe know who clicked it, what
they're clicking. So we can dolots of actions. But we can also
take them to a page, which showsthem in from a branded page,
which shows them maybe great,you want to stay another year,
(27:40):
you know, to review your bubble,blah, click here to review,
you're this click there. Andwe're giving them some
information there. So we'regetting an action from the
click, and doing something. Butwe're also then showing them
something that is branded,that's to me, one of the
simplest use cases where thisflies,
Pete Cuff (27:59):
it does with one caveat, which is you need to be
careful, because some some emailclients automatically scan and
ping and check email links thatare inside them. And so we've
seen use cases where forexample, someone said, you know,
you send out a link going clickhere, if you want to stay a
year. And for argument's sake,all of the Gmail addresses
(28:20):
instantly responded saying thatthey wanted to stay another
year. Ah, looks like Googleautomatically checks each. We've
never had that. So yeah, I can'tremember which emails, which
email provider it was. But we'vecertainly seen that and it's
been,
Jordan Fleming (28:36):
that would be irritating. Yeah, we've never
had that. But, but that is, Ithink it's a good example of
where External links can reallyhelp you where you've got
something, you've got an actionyou want them to take. That can
also be by the way embedded on awebpage, if you don't want to,
like there's lots of ways ofdoing it, you've got an action,
you want them to take somethingto click, and it's going to show
(28:57):
them a bit of information, maybesome links to new things. And
those are going to bedynamically generated each time
based on the context of whichbit of Podio you're linking to.
That is a great use case, but itcan be super fucking slow. So
you have to be very careful inhow you build, we've built
(29:17):
really complex ones that we'vehad to walk away from
eventually, because the loadtimes were like, now we're going
to have to we got to find abetter way of doing this.
Pete Cuff (29:27):
Sure. Another another kind of variation, I suppose at
the external link is kind ofrelated is that PWA can use a
create a CMS so contentmanagement system function. And
that's where you can say thatyou want PWA to create either a
single item or a table or aclick through table or you a
(29:47):
click through to the detail ofthat table from from an app or
an item in an app. And again,it's it's pretty basic. It's
quite good. It's an easy way toget information out. You can use
it in conjunction with externallinks as well. So you can, you
can say, you know, here's allyour stuff and click on here to
go and do something about eachone. But to be some of the kind
(30:11):
of cautions about it is that theCMS is technically I think, been
in beta for about 10 years. Andthat the the refresh time is
something like every 15 minutes.
And so it can lead to confusingresults when especially you've
got automations that are runningon something that someone's
done. But then they look back atthe CMS version, and it's all
(30:31):
cached, it's still showing whatwas true one minutes ago, or 14
minutes ago, let alone what'strue right now. So tread
slightly carefully on that.
Jordan Fleming (30:43):
Yeah, my honest opinion is, if you're gonna
start to the CMS functionality,isn't that useful. I think if
you're gonna really want to showthat you're gonna have to do it
with your own custom webapplication. If you really want
to show you really want to playin that. And which takes us to
the next kind of the final levelof this, just, you know, we're
(31:05):
going to today's podcast isreally a broad overview of the
ways the pitfalls, etc, that youcan do it. We'll dive probably
in the each of these in more inparticular, I will in the master
class as well. But the thirdcategory is really this, you
know, where you are taking Podiodata, and externalising it using
(31:26):
some sort of third party system.
You know, whether that is thirdparty system that you build or
third party system that you'reusing, via some other bit of
software. So let's start withyou know, you you identified it
as sort of skins in middleware.
And then and I would say skinsmiddleware and custom builds,
(31:49):
would be would be the three. Soit from a skins point of view,
we've got things like proc foo,and then low code, no code
systems like bubble.io. Let'sstart with proc foo, what are
your thoughts on proc foo isthis you know?
Pete Cuff (32:06):
I think I think profit is brilliant. So prop foo
have a, an option in the plancalled Mini Apps. And the idea
and the basic premise of a miniapp is you want exactly the kind
of use case that we're talkingabout here, which is Podio is
overwhelming, what you reallywant to do is just show three
fields, not 100. And you know,don't have to navigate through
(32:30):
load of workspaces and a load ofapps to get what you want, you
want to turn it into a miniwebsite. That's basically you're
saying, like a nice little miniwebsite that you can brand
however you want, structurehowever you want. And so that's
the kind of gap that many appshave gone into. They're they're
insanely customizable. The, youcan build incredible processes
(32:53):
both on the front on their frontend, and also, as a result in
your your back end in your inyour Podio platform. That the
biggest advantage that that Ithink that proxy Mini Apps has
over everything else now,really, is that it was built for
polio first. So it was built byAndreas who, originally, so I
(33:14):
get and the price. And theprice, I'll come to that price,
don't you worry. But yeah, itwas built by Andreas who
originally built globey flow,which is now Podio, workflow
automation. And it's the youwill struggle to find something
that is Podio centric. Podiotargeted, Podio compatible out
(33:38):
of the box for the price thatyou get, which is starting off
as free, and then going up to adizzying $9 When you start
paying for it. And then youknow,
Jordan Fleming (33:48):
when you get the Mini Apps
Pete Cuff (33:50):
bid, is it 25? Yeah, sorry,
Jordan Fleming (33:52):
$25 $25 a month to be able to do many apps is is
just insane. And a good usecase. So we've we've done a lot
of a tonne of Mini Apps over theyears we did a tonne when we had
game changers going. And I'msure that Andrew and his team
are doing a tonne still. AndI'll tell you, I'll show you
(34:13):
I'll tell you one really likesimple example, a timesheet. So
we built we used to havecompanies that had external
field teams, like I've saidbefore, and those guys don't
want to fuck around Podio theydon't want to fuck around Podio.
And and so we simply had atimesheet app, we built a mini
app on top of it, where anybodycould take we give them the
(34:35):
link. They could simply selectthemselves as an employee, you
could make it more complex andmake them login and do all that
shit. We didn't need to. We justwere like, here's here's a link
guys save it on your phone everyday. They click that little icon
on their phone, it pops up, theyselect their name, they click
and then they say I'm startingand then they they click and say
(34:58):
I'm stopping And it was a miniapp. And it was. And it was
super simple as externalising,as someone who wasn't in Podio
could just be, bam, bam, bam.
But internally, we got exactlywhat we needed. We got, here's
the employee start time, here'sthe employee's end time. And we
could use the genius of Podio,to work out all the billables in
the employ doubles and all therest of it. But for the user, no
(35:23):
Podio, no nonsense no Podio appon their phone, trying to
navigate it, just a very simpleform they could fill in.
Pete Cuff (35:33):
And all completely customizable, right and all
branded, however you wanted,
Jordan Fleming (35:37):
completely branded to them, customizable. E
for most of them, what we dideventually was actually give
them a kind of login, they couldlog you can set different ways
of logging into a mini app, wegave them a username and a
password, they logged in, andthey could see all their
timesheets for the whole year,they could review them, click on
them, see the information,update them, et cetera, update
(35:59):
them when if we let them or not.
And all of that driven in a kindof more web based environment
they were familiar with. Andthat
Pete Cuff (36:09):
gets over that that initial learning code, you don't
need to put them through thePodio journey, you don't need to
explain what this is everyoneknows how to use a website. So
this basically turns your Podiodata into a website. And one
critical thing that it alsoallows you to do, again, as a
differentiator between there sayopening the Podio app on your
phone, and entering a timesheetvia Podio native process is that
(36:31):
if you are a member of aworkspace in Podio, you can see
all the apps, all the data, allthe submissions in the timesheet
app, all of that stuff, not justyours, you can kind of make it
get that way. But at any point,you can say now just show me
everything. Whereas we'reprobably many apps, if you set
it up in the way that you wantto and if this is your use case,
(36:53):
then you can just say I onlywant to see today's records for
me.
Jordan Fleming (36:58):
Yeah, and and I actually want to broaden this
right now, because I don't wantthis pod This podcast is gone
for four hours. And I don't wantit to so I'm going to say this
is going to this is going to becheap and nasty, just like me.
And if we think aboutexternalising Podio data, I view
it as there's the the I don'tknow the Ford Focus. There's the
(37:24):
the Jeep Wrangler. And thenthere's the Ferrari, I don't
know, whatever, there'sbasically the cheap to the
expensive, right? The cheap isgoing to be proc for many apps,
is going to be kind of proc foominiapp type where you it proc
foo is very affordable, it'svery easy to create your cheap
(37:46):
is going to it's not ascustomizable. It's not to get it
going working really fast withlots of large data, you're going
to have to do some sort ofsequel sync in there to make
sure that happens. That the sortof cheap and I don't want to say
cheap and nasty, but the cheapand quick and wonderful is the
Mini Apps. At the superexpensive Ferrari fucking
McLaren f1 side, you've gotbuild your own web application,
(38:10):
where you are literally takingPodio data building some sort of
sequel sync, so that data flowsback and forth. And then you are
building an environment in aweb, you know, in a web
application where you are. Andthat is your Rolls Royce type
where you want someone to loginto hub.mydomain.com. And they
see a beautiful web applicationwith all their orders and their
(38:32):
customer information. And theycan update it. And we've built
lots of those. But they takemore time and a lot more
expensive. But of course, theygive a much better user kind of
interface, a brand experience.
And in the middle is sort ofyour bubble.io. Where I think
actually bubble.io is the is theleast of those, because proc foo
(38:53):
is brilliant and cost effective.
The other one is amazing andexpensive. And bubble is kind of
the worst of all worlds in someways. And I don't mean that as
disrespectful as it sounds,because it's good. But you're
not getting the flexibility ofbuilding your own shit, it's a
(39:15):
lot slower. And it's gonna takeyou a lot of time.
Pete Cuff (39:19):
So and you need to work out how to make it linked
to your Podio data, because it'snot built for poEdit. It's not
built for polio, it can talk topolio, but you need to make it
do it. Whereas a proc foo isbuilt to talk to polio, your
custom Ferrari isn't but theperson putting together would be
doing Podio integration for you.
Jordan Fleming (39:39):
And I think you if you're going to really think
about a use cases where sayyou've got customers and you
want them to log in and seeinformation in their orders or
their projects and, and be ableto give you updates and all that
but you don't want them in Podioyou've really got those two
pillars. It's either a proxymini app, or a custom web
(39:59):
application. My opinion and arereally the ways you want to
look. One is going to cost you alot less, but be less functional
and, and slightly less, youknow, design wise, you're gonna
have slight restrictions and allthat, but it's gonna be quicker
and cheaper. And one is going tobe where you really care about a
brand experience, etc. Andyou're building you're expecting
(40:21):
to spend 15 to $20,000 to builda web portal, like those, like,
to me, those are the only twothat matter in my opinion, what
do you think?
Pete Cuff (40:30):
Yeah, I completely agree. I think I think I want
bubble IO. And I like it to bemore Podio leaning than they
are, but they're not. So youknow, the strength that that
things like bubble might have isthat they are more suited also
say to dovetail straight intothe Google API and, and track
(40:51):
maps all over the place orintegrate to a payment gateway
or because again, that whatbubble? What bubble does is it
saying we're going to be yourown low code, no code, App
Builder service, you just linkit to what you want. And then
you can drag and drop this stuffaround. As I said, though, but
Podio isn't out of the box. Soit can't do that for Podio. It
(41:12):
doesn't.
Jordan Fleming (41:12):
Yeah, and I gotta say, I mean, we did a
project a couple years ago. Andyou know, that's a project we
did a couple years ago, usingbubble.io. And it may have
improved a lot. But it, itwasn't very, the problem is, and
particularly if you've beenused, so used to using Podio. If
(41:34):
you're really used to buildingin Podio, you used to being able
to do almost anything withCitrix. PWA like spoils us,
because you can do almostanything, add in proc foo and
fucking you can do anything. Anddo it quickly. And the problem
is when you that, that sets yourexpectations, that everywhere
(41:59):
else their workflow automationcan be done that quickly and
that brilliantly and bubblesimply wasn't there. It maybe it
is now maybe it is now but itjust wasn't there. And so we
ended up with I we ended up likefeeling like we were walking
through treacle, you know, likemolasses when you were trying to
(42:19):
do this. So really, I think yourbest options are proc food. I
think proc for many apps, if Iwas going to say to anyone who
wanted to get started onexternally externalising Podio
data right now proc foo.com.
Fucking buy an account and readup on many apps because I can I
and I don't build in Podioanymore, and I haven't built in
(42:44):
Podio. Really for three years, Ican still put together a mini
app in 20 minutes, which doeswhat I need it to do. It's not
gonna have lots of bells andwhistles, but it's that sort of
it's got the Podio do ityourself, feel. But your results
can be really quite nice.
Pete Cuff (43:05):
Yeah, agreed. And again, it is like all these all
these things, all the stuffwe're talking about. The more
you delve into it, the more youunpick it, the more you pull it
stuff, you'll find more and moreand more options, more and more
possibilities. But equally, thenthe more complicated, you're
making it. So it's more likelythat you're going to need to
learn some coding elements aswell in order to get the
(43:26):
absolute most out of it. Butyou're right, that it's in
various places. It's kind ofjust dropship, press this
button, and I think Andres hasreleased the ninja that can
build a mini app for you in like30 seconds.
Jordan Fleming (43:43):
Comparatively, if we're talking about you know,
I mean, you've got a Podioconsultancy, you build Podio for
people all the time. You know,you guys, I'm sure that, you
know, you can build the time ittakes to build a Podio miniapp
even one that's relativelycomplex, compared to the time it
(44:04):
takes to build a web applicationfrom scratch. Yeah, even if
you're using a symphony or, youknow, one of these kinds of
coding structures, even ifyou're using that the time, you
know, in eight to 10 hours of ofwork, you can get an enormous
amount done versus eight to 10hours in a web application is
(44:25):
like well, okay, we've gottenstarted this year, right and,
and so really like that's whatI'm saying it's I don't I don't
mean it to be disrespectful whenI say a Ford versus a Ferrari.
Because actually, you know, thatyou're all I'm talking about is
you know, it's more it's notabout Ford versus Frey so much
as it's, you know, one there arerestrictions, but the cost and
(44:48):
speed are a massive advantage.
The other costs and speed gomassively down but the results
are up. Unbelievable. So youwhere's your sweet spot? Do you
You need to spend $35,000,building a web application a
complex web application that isall singing, all dancing and is
exactly branded and above law,when probably not, if you know,
(45:09):
in which case, you know, fivegrand will get you a tremendous
amount and a miniapp stage.
Yeah,
Pete Cuff (45:17):
you could do that, you know, a miniapp is a great,
a great proof of concept, youcan get there on an iterate
quickly, you can get it to testout your processes and how it's
going to work in the back end.
And if you really decide thatyou want more power, more grunt,
more speed, more, whatever ismissing, then you could take
that mock up for want of abetter way of putting it and so
and give that to a developersaying make that but do it over
(45:39):
here?
Jordan Fleming (45:41):
Absolutely. All right. Well, listen, I think
that's a pretty good overview ofthe ways, I would sum this up by
saying, you know, if you simplyif you want to simply show
people a bit of data, anexternal link, or a, you know,
there, there are ways of doingthat, that are pretty easy. I
(46:04):
would say, only bring peopleinto Podio. If you're going to
seriously bring them into Podio.
If you're not going to seriouslybring them into Podio,
investigate one of these othersystems, other ways of doing it.
And if you're going to reallytry and externalise a lot of
data, the best option is a miniapp or a web portal, the miniapp
being much quicker and muchcheaper, with some more
restrictions, the web portalbeing all singing, all dancing,
(46:26):
and budget is your only limit.
Right? So I mean, start to thinkabout what you know, start, I
would say, start to think about,what does it mean to me to
externalise Podio data? Who do Iwant to see it? What do I want
them to see? How do I want themto interact with it? And if you
(46:50):
answer those questions, it'lllead you to the way and if
you've got any questions, justdrop Pete a line, I'm going to
drop his contact informationinto the podcast information,
drop PETA line, or head over towe are game changers.com, you
can fill in a Podio a partnerrequest, I've got a whole group
of partners in which Pete is oneof them, where I can match you
(47:12):
up. But Pete has a huge amountof knowledge in this. His
contact details will be in thepodcast information. So please
do drop them a line.
Pete Cuff (47:21):
Thank you very much.
Jordan Fleming (47:23):
I Pete I gotta go. My daughter has a recital
and I am not going to miss it.
So So yeah, and I'm also headingoff to Italy tomorrow.
Unknown (47:34):
So I'd like to some of us say,
Jordan Fleming (47:38):
Yeah, I'm going on holiday. So this, this will
come out in a couple of weeks.
Pete Cuff (47:42):
All right. Well, thanks very much, Sheldon, been
great to talk to you.
Jordan Fleming (47:45):
Thanks so much for joining us. And thank you
guys, for listening. Pleaseremember to Like share, click
things that you're supposed tocollect and make sure that you
spread the gospel of Podio viathe supercharged podcast.
Narrator (47:59):
You've been listening to another awesome episode of
supercharged with Jordan SamuelFleming don't forget to hit the
subscribe button on our YouTubechannel to be notified of new
podcast episodes Podiomasterclasses and in depth Podio
extension reviews if you'veenjoyed this podcast, please
give us a review on your podcastplayer to help support the show
Welcome to the supercharged with Jordan Samuel
Fleming, your weekly podcastdedicated to what your business
can achieve when it's powered byPodio. Join us each week as we
learn from the top Podiopartners in the world as we
investigate system integrationsand add ons and hear from real
business owners who haveimplemented Podio into their
(00:21):
business. Now join Jordan SamuelFleming, CEO of smartphone for
this week's episode.
Jordan Fleming (00:28):
Hey, everybody, and welcome to this week's
episode of supercharged I'm yourhost, Jordan, Samuel Fleming,
here to talk all about the powerof workflow and automation, when
your business is powered byPodio. Well, this episode, this
week's episode brings backanother returning champion for a
very specific reason. I broughtback Pete cough from future
(00:50):
solutions. A Podio partner, justlike I used to be does a lot of
building inside of Podio. Andwe're here to talk about a very
specific thing that we get askedabout all the time, which is how
do I share Podio data withpeople outside of Podio? What
are the best practices and Peteand I dive into this a little,
it kind of goes along with amasterclass that I'm putting up
(01:11):
right now. It's showing you thisin a more direct way. But what
are the ways you can share data?
What are the pros of each way ofdoing so? What are the cons?
What are the best practices?
What are the options you haveavailable to you? You know, we
all know, and certainly if youlisten to this podcast,
hopefully, you'll hear mypassion about how amazing Podio
is to manage the business, dothe workflow, you know, share
(01:37):
information across your team.
But what about those times whenI need to show a customer
something I need to bring acontractor in and show them
something Podio is built forthat in many ways. And we go
through in this podcast, thekind of different opportunities
you have, and the pros and consaround them. As always, please
do make sure you head over theYouTube channel, give us
(01:59):
subscribe, make sure you're upto date on the masterclasses, go
to your podcast platform, giveit a like and a share, give it a
rating, it really does help tospread the gospel of Podio. And,
of course, as always enjoy thisepisode, very special episode
talking about how to share Podiodata outside of Podio. With Pete
cuff, let's have a listen.
(02:28):
So we decided that for thisepisode, we would focus on kind
of deep diving into sharingPodio data, right? Like, you
know, and for those who I shouldprobably start out with today's
guest, as you've heard from theintroduction is Pete cut from
future solutions. And pizza,very old, old old photo partner,
(02:57):
his company future solutions,build systems support systems.
And when we were chatting about,you know, things that we thought
would be useful for the podcast,we always try and make sure we
come up with ideas that will beuseful. We talked about this
notion of sharing Podio datawith other people. And that's
really where we want to kind offocus on today and discuss the
(03:21):
different ways you canachievement. And also kind of
pros and cons about it. Right?
Yeah, so
Pete Cuff (03:27):
one of the one of the kind of great things about Podio
is when you're in it, it allmakes sense. But when you're
when you're out of it, or you'rejust starting to get into the
first time, it can be veryconfusing, very overwhelming.
And, you know, first andforemost, Podio is a
collaboration platform, it'smeant to bring people together
into one place, but sometimesthat place can be a bit too big
(03:50):
or too you know, you don't wantto share 100% of everything, you
just want to share 1% of whatyou want that one person to see.
So that's when these differentkinds of methods can come in
handy.
Jordan Fleming (04:01):
That and I think you know, because so many of us
build, you know, Podio becomesusually a real powerhouse of
your business, right like it, itends up kind of touching and
bringing in so much of your dayto day kind of business that you
(04:23):
end up having a lot of data inthere that you may want to share
with someone outside of yourorganisation, an accountant or a
consultant or contractors orwhatever that is customers. And
because Podio is so powerful atthat part. The next logical step
is how do I externalise some ofthe amazing things I've done in
(04:46):
my Podio How do I get theresults are the information into
someone else's hands? So it'sit's not even just about you
know, about the somewhat kind ofconvoluted onboarding. It's all
So about, you may never wantpeople to know what Podio
exists, sometimes, and sometimesyou do want them to know Podio
exists, or sometimes you don'tcare that Podio exists. And each
(05:09):
use case has its value. So ifit's okay with you, Pete, I'm
going to drive the the firstpart of this to say, I want to
focus on this in two parts,that's using the word part way
too many times I understand. So,part one will be an, you know, I
want to focus on sharing Podiowith other people. And part two
(05:34):
will be sharing Podio data usingan external vehicle of some
sort. Because there are amultiple different ways of using
Podio. And sharing things withthe native Podio kind of
structure. And there are plusesand minuses all of them. So if I
think about a Pete, I'm thinkingof, you can share an item, you
(05:58):
can bring people into Podio intoa workspace, and you can use a
native webform. Those would bethe three that I would class as
part one, right? That is you'reusing Podio. And you are
exposing people to Podio in a ina certain way. So let's talk
about those first. Why do youthink you know, if we go through
(06:21):
those three, where are theygood? When are they bad? When
are they in between? What do youthink? Okay,
Pete Cuff (06:25):
well, let's start I suppose with probably the
easiest one, which is to sharean individual item, interact
with with somebody else. Sofirstly, the logistics of how
you actually do that istypically on say, the comments
field on the right hand side,you can just do an act symbol,
and then start typing insomebody's email address. And
(06:46):
that will start sharing when youthen send that message, you
write a comment to them, sendthem that message, they will
then receive an email from Podiowith Polios, branding, polios
name, etc, on it, saying, youknow, Jordan shared this with
you or Jordan said this to you.
And then it will have a, youknow, a snippet of what's going
on. And it will have a buttonsaying click here to reply or
(07:08):
click here to go and have alook. And that, in itself is
brilliant, because it putseverything that you need just
onto one email, everybody knowsand trusts email, it's very
familiar. And of course, it'sit's read only as well, at that
point, they can't they can'tchange anything, they can't do
(07:29):
anything with it. Now I'll kindof spare the details of once
they're in, you can change thosepermissions and so forth. But
what it will then do and driveis that that person, then in
order to see that item needs tocome and open a Podio account.
Jordan Fleming (07:46):
And that's where it all falls down. Yeah, that
Pete Cuff (07:49):
Citrix is model.
Yeah, that makes sense. Right?
Jordan Fleming (07:53):
I mean, it makes sense. But it is a massive
weakness of this type ofsharing. Because a it drives the
necessity of I gotta create anaccount for this shit. Like, you
know, so you know, there's thatproblem. And the second problem,
I think, because, you know, wecould spend 40 minutes just on
(08:14):
this bit, and other and nobodywill learn anything. The second
problem is, it's really a clunkyway of sharing information,
because there's no filtering, orsorting or organising that which
as you have shared with you. Sowhen that person even if I'm a
Podio user already, but I'm in adifferent company, if you share
(08:36):
me something an item, it goesinto my shared with you section.
And there's no filtering, nosorting, no searching. And so
beyond a handful of things, itbecomes a fucking pain in the
ass.
Pete Cuff (08:53):
I knew it wouldn't be long before various exclusive
left your mouth when it came onabout that process. Yeah, you're
right. It's really annoying,it's fantastic. If you've only
got one or two things that youwant to share with the person,
that's where it comes into itsown. That's great. And also it
works well. If you're able sayto talk to that person first.
And say by the way, you're goingto receive an email, it's from
(09:15):
our system Podio you'll need toopen an account, don't worry,
it's all free, follow this stuffon on screen and you'll be fine.
And as long as you can kind ofgive them that warning that this
stuff is about to happen, thenit can probably start to make
sense. I accidentally shared anitem with a friend recently
sorry, way back in the day. Andhe replied back saying So go on,
(09:35):
then what's this Podio thing andI had to kind of explain it's
this big old system. Sorry, Ididn't mean to do it. I couldn't
pull it back. And it was justlike well, it would have been a
lot easier. If it was he was onthe phone at the time that I did
it. I mean I said that checkyour inbox now you've got a link
Yeah, so that's that's thethat's the first one but yeah,
the downside is most definitelythat you go on to the Citrix is
(09:59):
Citrix is onboarding journey,which is clunky as hell, and
doesn't make sense, and they tryand explain what everything is,
when really, it's justpointless. Well,
Jordan Fleming (10:10):
there's that.
And then that leads us into whatI would class as the next step
up, which is sharing bringingsomeone into a workspace right?
Now that is a big step up inthat it can become a truly
collaborative tool with anexternal group of people, you
can very successfully and I havemyself and seen many of our
customers very successfullybring in external teams into
(10:33):
workspaces, and have them startto love Podio, you know, and
save them really get you going.
So this, this is a definite stepup in that what you're doing at
this stage is you're actuallybringing them into a workspace
or multiple workspaces, butusually just one. And you're
essentially when you do that,you're giving them the
(10:55):
opportunity to use theworkspace, the apps and
everything, see everything asthough you they normally would.
And that means that they cancollaborate with you, like any
Podio user can. But of course,as Pete, I'm sure we'll both
point out. The downside of thatis if you're bringing people in
(11:15):
who don't need to be in Podio,very often, you're essentially
going to be a Podio helpline forthem, because they're going to
come in every month to see theone thing you need them to see.
And they're going to be like,What the hell? Where do I go?
How do I you know, that thatwhole onboarding process when
you get a new staff into Podio,and the time it takes for them
to learn it? You have to do witheverything? Everybody over and
(11:36):
over again?
Pete Cuff (11:38):
Absolutely. And it's complicated, because it's
unusual. People aren't, youknow, people don't know how to
use Podio out of the box, youdon't know what workspaces,
yeah, the first time I loggedinto Podio, and took out an
account, I didn't get it. And Inearly closed my account and
walked the other way. I'm veryglad I came back a few years
later, and gave it another try.
And it finally started to makesense to me. But there's a huge
learning curve. And you eitherget it or you don't. And most
(12:00):
people don't, in my in myexperience, and the thing that
when you add someone into aworkspace, if you are getting
them in my my advice would bewhatever that workspace is, in
the first instance, make it assimple as possible. So for
example, one of our clients usedit as a way to have a forum for
their, for their customers. Andthey had several 1000 external
(12:22):
users in that in that workspace.
And yes, most of them didn'tengage with it, but some really
got it. And you know what it'slike when you go into a forum,
and you see, you know, the sameold names over and over and over
again, it's like it did, therewere people who got it, and
they, they just need to get to acertain point to make it work.
But it's a real challenge, Ithink, to get people to
(12:45):
understand it. And one of theways that you could seek to
improve that, as I've saidbefore, firstly, ideally have
someone on the phone or inperson and show them through it.
But for purposes of scale, whynot record your own onboarding
journey, why not record your ownvideo showing them this is the
workspace that you're going tobe a member of, or a sample of
(13:05):
it. This is what you click on,this is an ad, this is the
activity stream, etc, etc. Andthen you can really target your
message and get those users toonly see the stuff that you
really want them to focus on.
Jordan Fleming (13:18):
I agree with that. And the second thing I
would say about that is thatthis is really in my opinion,
this is really only applicablefor the people you want to be
working in Podio with on a veryregular basis. You know, it
doesn't really matter how simpleyou make the workspace, if
they're only going to see itonce a month, find us one of our
(13:39):
other methods we'll talk aboutbecause it's not worth the
hassle. But like if you've gotI've seen people bring customers
in very successfully to Podioand contractors, subcontractors
etc. And as long as you have a,a clear and an obvious workspace
with a very few set of apps thatmake complete sense. And they
(14:01):
people are working in there allthe time, it can be incredibly
powerful, because you suddenlyhave all the collaboration that
you're used to, but you've gotit with people who are outside
of your organisations, you gotsubcontractors who are managing
a project with you, and they cansee everything and comment and
assign tasks and do tasks. Andso there's huge value to that.
And I can't stress enough thefact that Podio is business
(14:23):
model is to its credit in thisway, you can bring an unlimited
amount of external users intoyour organisation and for free,
and that is not something thatmost of these systems have. And
that means that if you can getthis model working, you can
actually bring a lot of peopleinto your system, have them
(14:46):
fully working inside it, and youare not paying a monthly fee for
those people. So that's a hugebenefit to that model.
Pete Cuff (14:53):
Absolutely. Yeah. And I'd like it also a bit to say
Google's model which is youknow, you can You can attach a
Google doc to a email. But whatyou really want to do is open a
Google account. So you can nowcollaborate on that item life.
It's kind of that similar modelof if you can get them in and
explain to them what this is,then that you really start to
reap the benefits on the otherside.
Jordan Fleming (15:15):
100% 100% agree with that. And, you know, and
just to round out the internalkind of Podio bits, because I
don't, I want to get through allof these today, if we can.
There's one final one, which iskind of using the internal bits
of Podio, which are prepopulated web forms. So if we
think about it, the first one isthe one I never recommend, which
(15:37):
is simply to share an item. Itis the worst case, you know, in
my opinion, bringing people intothe workspace is the second one,
which can be hugely powerful,and has huge benefits, but has
to be done in a specific andcontrolled way. And then the
third one is the individualprefilled webform. So Pete, why
(15:58):
don't you tell us a bit aboutthat.
Pete Cuff (16:00):
Okay, so the prefilled webform, that's the
one where you're going to needthe most level of, I'd say
coding slash planning to makethis work for you. But that the
flip side of that is that it'svery, very powerful, if used
correctly. So every single appin Podio can be turned into a
webform in just a couple ofclicks. That means that external
(16:22):
users can populate the whicheverfields you set to be shown with
the data. So it's like they'rein Podio, and putting in the
data themselves. But it's alldone at arm's length outside of
Podio. Looking in. Now, how youpre populate fields on a
webform, because when it firstloads, it will be blank. How you
(16:45):
pre populate it is your pins, aquery string. So that's a set of
parameters and values to the endof the URL, the website address
for that, for that webform. Andit means you can do things like
let's say you've given eachcustomer or client of yours an
ID that you want them to cite ora code to put in to get a
(17:09):
discount or something like that,it means that you can pre
populate that field so that whenthey arrive, it's already there.
Now the details of how to dothat are documented more in the
Podio help documentation, Ithink I'd recommend working
through that in person ratherthan trying to explain it over a
podcast. But the basic premiseis you have the the URL of the
(17:32):
webform, a question mark, andthen you set like field X equals
ABC field y equals 123. And itwill populate.
Jordan Fleming (17:43):
Now hugely powerful this hugely powerful,
Pete Cuff (17:46):
because you can make it do really clever stuff,
especially when you then combineit with a little bit of styling,
so a little bit of HTML and CSSstyling. And that's basically
what makes the form look the waythat it does. So it comes with
forms out the box comes withlots of different styling
options that you can choose froma drop down. But then there is
an option also on that stylingbit to to add custom styling to
(18:08):
Custom CSS. And that's where youcan do things like hide a field.
So you could use your querystring up in your in your
address bar, to say that youwant to set the ID fields to
123. And then you can set yourCSS your styling to say and hide
field ID so that it's beingpopulated that they can't, the
(18:28):
person looking at the webform,when the filling in can't see
that the ID is alreadypopulated. And most importantly,
they can't remove the ID, theycan't hide that they can't
change it accidentally. So it'sreally powerful say to, you
could you could populate it withsomebody's first name and last
name so that they know thatthey're that you know, you've
(18:48):
got their data or you know thattheir name or their email or
whatever, but you might want tohide how you got to that point.
So
Jordan Fleming (18:56):
I'll give you a great example of real life
example, which shows just howthis little thing can can make
your system so easy. And that iswe build a system years ago for
a training company that like didoutdoor training and adventure
stuff. And so they would have,they would have a customer, they
(19:19):
would have people who registerfor their stuff for their
events. And then they will wantto maybe get dietary information
and sizing and whatever. And sowe simply used globey flow PW
Citrix PWA to create the URL bydropping in tokens, right by but
by dropping in. So I could getthe name from one app and the
(19:42):
event ID from another app. And Icould do all that because again,
you've got the power of CitrixPWA to grab information from all
over the place, create this URL,which meant that when they
clicked we got they got theautomated email that said, hey
Jordan, it's time for you toyour event. Just two weeks away,
it's time for you to give usyour fucking dietary
(20:03):
information. They clicked on thelink, and it populated and it's
like Jordan, the name is JordanFleming the event is, you know,
camping inactive, the dietaryrequests or beer, beer and
meats, and etc, etc, etc. And itwas all prefilled with the
information about the event andme. And then I could simply do
the bits that I needed, andupdate bits, like my contact
(20:27):
information and choose that. Andthen it went into Podio. And we
knew exactly what it was whatevent it was for, we got
everything in for there, theydidn't have to type in a bunch
of fields they are they didn'thave to do their name. Again,
they didn't. And moreimportantly, they didn't have to
do things where they could fuckup the results I needed. So like
an event ID or Person ID, youknow, when I needed to make sure
(20:48):
that this was going to registeras Jordan Fleming, I don't want
to put that in their hands. Andthat's one of the powerful
things about web, the webforming elements. The way Pete's
talking of is, if you reallytake it to the way it can be
done, you can take informationfrom all over your Podio system,
pre fill the bits in the form,and give someone a really guided
(21:12):
experience where all you need todo is gather a bit of data.
That's all you need. Okay, handsup who's using Podio for real
estate, and they don't want moreLeads. Nobody. You want more
Leads closed, well check outsmartphone for Podio, the only
phone system fully built forCitrix Podio. With an fully
integrated power dialer and ouramazing mobile apps, it means
(21:35):
wherever you are, you can makemore calls, love to Podio, send
more texts, love to Podio andclose more deals all log to your
Podio CRM, click the link, checkit
Pete Cuff (21:46):
out. But then that leads us simultaneously so
nicely on to the kind of con ofof this approach, which is that
web forms are just catch tools,they only receive information.
So whilst you might be able topre fill them for them, you are
still then receivinginformation, you're not updating
anything, it's creating a newitem. Yeah, it creates a brand
(22:09):
new item in the app populatedwith whatever they have
submitted on that form, whetherthat's prefilled or not. And
therefore that a importantconsideration, I want to think
about when using prefilled, orblank Web Forms is generally
speaking, it's best to justremember everything, there's a
catch, and therefore there couldbe duplicates. And if you are
(22:30):
wanting to update a record as aresult of receiving a webform,
you need to use either manual,but more preferably an automated
approach to check that the firstthing that you get through then
goes off and updates the masterrecord, wherever that may be
somewhere else. And just treatit all as like a big intro, and
(22:50):
then work out how to deal witheach one as it comes in.
Jordan Fleming (22:53):
Yeah, it is much better, as in my opinion, it is
much better as a way ofgathering information rather
than updating. So you can use itto like, hey, update your
contact details, you know, this,you can do that. But it's gonna
require you to create a new itemand then check and replace, or
whatever and, and there arebetter ways that we'll talk
(23:16):
about in a second to doing thatsort of thing. But where this
comes into its own are thingslike the use case I gave you
where, you know, I've got anevent I'm running, and I'm
trying to gather, you know,information from someone about
their next of kin and theirdietary, those are perfect,
because what you're really doingis you're using the prefilled
bits to identify the parts youneed to ident like this, it's
(23:39):
this person for this event onthis date, etc. And you pre fill
in that bit so that you theycan't touch it, and you're
gathering new information you'venever had. That's where this use
case fucking flies in myopinion.
Pete Cuff (23:52):
Yeah, absolutely agreed. Yeah, as I said,
Remember, it's a catching tool.
It's not an updating tool.
Jordan Fleming (23:58):
Yeah, absolutely. Now, a last one I'm
going to touch on although Ithink this will deserve its own,
I'm gonna do its own. I may getAndrew and maybe you on a group
one to talk about it. Because Iwant to dive in more into the
capabilities of a PWA ExternalLink. Because I don't want to
(24:18):
I'm not gonna dive too much intoit on this episode, because it's
a long fucking narrative that wecould drive it for a while. But
the last kind of internal thepodium, one, in my opinion, is
an external link. And it's thethis is the one that bridges the
gap between using just Podiotools and kind of externalising
them and using some of the othertools we're about to talk about
(24:39):
and an external link issomething that you can create in
globey flow in Citrix PWA. Andessentially, it creates a unique
link that can be clicked on. Andyou can actually make the page
it goes to do almost anything.
So you can display data, you candisplay tables, you can Get
referenced items from all overyour Podio create tables and
(25:01):
buttons, and links to new webforms, you can create it as a
holding page or as a sort of asplash page, which then links to
a bunch of things. It can beamazingly powerful. But it also
is slow. Very. So if you thewarning is it's great to use in
some circumstances. But if youpush it too far, and we've
(25:25):
pushed it too far, if they're onlike a 3g, 4g connection, it is
not a sensible option, would youagree
Pete Cuff (25:36):
completely. And in its most pure form, when you say
in PWA, I want to create a newexternal link for this for this
app for this item, the firstbrick that it automatically puts
in on on the flow is a web a webpage, brick. And what some
people don't realise is that asyou've just then said, whilst it
(25:57):
puts it in at the top, and thenyou can put more things
underneath, you can change thatorder. And put in your get
referenced, you can buildtables, you can build variables,
you can do whatever the hell youlike, and then show the web
form, sorry, not the web formthe web page. But that's the
problem is that whilst anythingthat you've put above the web
page is going on the web page isnot loading. So the person at
(26:20):
the other end is waiting for aprocess. So all they're seeing
is a blank white page, waitingfor the web page bid to be
triggered and come in. And soit's yeah, it should be used
carefully and infrequently wouldbe my steer,
Jordan Fleming (26:36):
I have a great success in using this in where
we've maybe sent an email. Andin that email, we've got an
action button. You know, do youwant to confirm that you love
cheese? Yes. So you know, andthey action button is yes. And
(26:58):
when they are now let's give areal example, a property
management example where thelease is up for renewal, and
we're going to send them a 90day notice that it's up for
renewal, is it your intention tostay another year, you know, and
click here to tell us you wantto stay another year, click here
to tell us who you don't. Andwhen they click here to say they
(27:19):
want to stay in the year, we'reusing a Podio. A CD is Citrix,
PWA, external length, which thenwe know who clicked it, what
they're clicking. So we can dolots of actions. But we can also
take them to a page, which showsthem in from a branded page,
which shows them maybe great,you want to stay another year,
(27:40):
you know, to review your bubble,blah, click here to review,
you're this click there. Andwe're giving them some
information there. So we'regetting an action from the
click, and doing something. Butwe're also then showing them
something that is branded,that's to me, one of the
simplest use cases where thisflies,
Pete Cuff (27:59):
it does with one caveat, which is you need to be
careful, because some some emailclients automatically scan and
ping and check email links thatare inside them. And so we've
seen use cases where forexample, someone said, you know,
you send out a link going clickhere, if you want to stay a
year. And for argument's sake,all of the Gmail addresses
(28:20):
instantly responded saying thatthey wanted to stay another
year. Ah, looks like Googleautomatically checks each. We've
never had that. So yeah, I can'tremember which emails, which
email provider it was. But we'vecertainly seen that and it's
been,
Jordan Fleming (28:36):
that would be irritating. Yeah, we've never
had that. But, but that is, Ithink it's a good example of
where External links can reallyhelp you where you've got
something, you've got an actionyou want them to take. That can
also be by the way embedded on awebpage, if you don't want to,
like there's lots of ways ofdoing it, you've got an action,
you want them to take somethingto click, and it's going to show
(28:57):
them a bit of information, maybesome links to new things. And
those are going to bedynamically generated each time
based on the context of whichbit of Podio you're linking to.
That is a great use case, but itcan be super fucking slow. So
you have to be very careful inhow you build, we've built
(29:17):
really complex ones that we'vehad to walk away from
eventually, because the loadtimes were like, now we're going
to have to we got to find abetter way of doing this.
Pete Cuff (29:27):
Sure. Another another kind of variation, I suppose at
the external link is kind ofrelated is that PWA can use a
create a CMS so contentmanagement system function. And
that's where you can say thatyou want PWA to create either a
single item or a table or aclick through table or you a
(29:47):
click through to the detail ofthat table from from an app or
an item in an app. And again,it's it's pretty basic. It's
quite good. It's an easy way toget information out. You can use
it in conjunction with externallinks as well. So you can, you
can say, you know, here's allyour stuff and click on here to
go and do something about eachone. But to be some of the kind
(30:11):
of cautions about it is that theCMS is technically I think, been
in beta for about 10 years. Andthat the the refresh time is
something like every 15 minutes.
And so it can lead to confusingresults when especially you've
got automations that are runningon something that someone's
done. But then they look back atthe CMS version, and it's all
(30:31):
cached, it's still showing whatwas true one minutes ago, or 14
minutes ago, let alone what'strue right now. So tread
slightly carefully on that.
Jordan Fleming (30:43):
Yeah, my honest opinion is, if you're gonna
start to the CMS functionality,isn't that useful. I think if
you're gonna really want to showthat you're gonna have to do it
with your own custom webapplication. If you really want
to show you really want to playin that. And which takes us to
the next kind of the final levelof this, just, you know, we're
(31:05):
going to today's podcast isreally a broad overview of the
ways the pitfalls, etc, that youcan do it. We'll dive probably
in the each of these in more inparticular, I will in the master
class as well. But the thirdcategory is really this, you
know, where you are taking Podiodata, and externalising it using
(31:26):
some sort of third party system.
You know, whether that is thirdparty system that you build or
third party system that you'reusing, via some other bit of
software. So let's start withyou know, you you identified it
as sort of skins in middleware.
And then and I would say skinsmiddleware and custom builds,
(31:49):
would be would be the three. Soit from a skins point of view,
we've got things like proc foo,and then low code, no code
systems like bubble.io. Let'sstart with proc foo, what are
your thoughts on proc foo isthis you know?
Pete Cuff (32:06):
I think I think profit is brilliant. So prop foo
have a, an option in the plancalled Mini Apps. And the idea
and the basic premise of a miniapp is you want exactly the kind
of use case that we're talkingabout here, which is Podio is
overwhelming, what you reallywant to do is just show three
fields, not 100. And you know,don't have to navigate through
(32:30):
load of workspaces and a load ofapps to get what you want, you
want to turn it into a miniwebsite. That's basically you're
saying, like a nice little miniwebsite that you can brand
however you want, structurehowever you want. And so that's
the kind of gap that many appshave gone into. They're they're
insanely customizable. The, youcan build incredible processes
(32:53):
both on the front on their frontend, and also, as a result in
your your back end in your inyour Podio platform. That the
biggest advantage that that Ithink that proxy Mini Apps has
over everything else now,really, is that it was built for
polio first. So it was built byAndreas who, originally, so I
(33:14):
get and the price. And theprice, I'll come to that price,
don't you worry. But yeah, itwas built by Andreas who
originally built globey flow,which is now Podio, workflow
automation. And it's the youwill struggle to find something
that is Podio centric. Podiotargeted, Podio compatible out
(33:38):
of the box for the price thatyou get, which is starting off
as free, and then going up to adizzying $9 When you start
paying for it. And then youknow,
Jordan Fleming (33:48):
when you get the Mini Apps
Pete Cuff (33:50):
bid, is it 25? Yeah, sorry,
Jordan Fleming (33:52):
$25 $25 a month to be able to do many apps is is
just insane. And a good usecase. So we've we've done a lot
of a tonne of Mini Apps over theyears we did a tonne when we had
game changers going. And I'msure that Andrew and his team
are doing a tonne still. AndI'll tell you, I'll show you
(34:13):
I'll tell you one really likesimple example, a timesheet. So
we built we used to havecompanies that had external
field teams, like I've saidbefore, and those guys don't
want to fuck around Podio theydon't want to fuck around Podio.
And and so we simply had atimesheet app, we built a mini
app on top of it, where anybodycould take we give them the
(34:35):
link. They could simply selectthemselves as an employee, you
could make it more complex andmake them login and do all that
shit. We didn't need to. We justwere like, here's here's a link
guys save it on your phone everyday. They click that little icon
on their phone, it pops up, theyselect their name, they click
and then they say I'm startingand then they they click and say
(34:58):
I'm stopping And it was a miniapp. And it was. And it was
super simple as externalising,as someone who wasn't in Podio
could just be, bam, bam, bam.
But internally, we got exactlywhat we needed. We got, here's
the employee start time, here'sthe employee's end time. And we
could use the genius of Podio,to work out all the billables in
the employ doubles and all therest of it. But for the user, no
(35:23):
Podio, no nonsense no Podio appon their phone, trying to
navigate it, just a very simpleform they could fill in.
Pete Cuff (35:33):
And all completely customizable, right and all
branded, however you wanted,
Jordan Fleming (35:37):
completely branded to them, customizable. E
for most of them, what we dideventually was actually give
them a kind of login, they couldlog you can set different ways
of logging into a mini app, wegave them a username and a
password, they logged in, andthey could see all their
timesheets for the whole year,they could review them, click on
them, see the information,update them, et cetera, update
(35:59):
them when if we let them or not.
And all of that driven in a kindof more web based environment
they were familiar with. Andthat
Pete Cuff (36:09):
gets over that that initial learning code, you don't
need to put them through thePodio journey, you don't need to
explain what this is everyoneknows how to use a website. So
this basically turns your Podiodata into a website. And one
critical thing that it alsoallows you to do, again, as a
differentiator between there sayopening the Podio app on your
phone, and entering a timesheetvia Podio native process is that
(36:31):
if you are a member of aworkspace in Podio, you can see
all the apps, all the data, allthe submissions in the timesheet
app, all of that stuff, not justyours, you can kind of make it
get that way. But at any point,you can say now just show me
everything. Whereas we'reprobably many apps, if you set
it up in the way that you wantto and if this is your use case,
(36:53):
then you can just say I onlywant to see today's records for
me.
Jordan Fleming (36:58):
Yeah, and and I actually want to broaden this
right now, because I don't wantthis pod This podcast is gone
for four hours. And I don't wantit to so I'm going to say this
is going to this is going to becheap and nasty, just like me.
And if we think aboutexternalising Podio data, I view
it as there's the the I don'tknow the Ford Focus. There's the
(37:24):
the Jeep Wrangler. And thenthere's the Ferrari, I don't
know, whatever, there'sbasically the cheap to the
expensive, right? The cheap isgoing to be proc for many apps,
is going to be kind of proc foominiapp type where you it proc
foo is very affordable, it'svery easy to create your cheap
(37:46):
is going to it's not ascustomizable. It's not to get it
going working really fast withlots of large data, you're going
to have to do some sort ofsequel sync in there to make
sure that happens. That the sortof cheap and I don't want to say
cheap and nasty, but the cheapand quick and wonderful is the
Mini Apps. At the superexpensive Ferrari fucking
McLaren f1 side, you've gotbuild your own web application,
(38:10):
where you are literally takingPodio data building some sort of
sequel sync, so that data flowsback and forth. And then you are
building an environment in aweb, you know, in a web
application where you are. Andthat is your Rolls Royce type
where you want someone to loginto hub.mydomain.com. And they
see a beautiful web applicationwith all their orders and their
(38:32):
customer information. And theycan update it. And we've built
lots of those. But they takemore time and a lot more
expensive. But of course, theygive a much better user kind of
interface, a brand experience.
And in the middle is sort ofyour bubble.io. Where I think
actually bubble.io is the is theleast of those, because proc foo
(38:53):
is brilliant and cost effective.
The other one is amazing andexpensive. And bubble is kind of
the worst of all worlds in someways. And I don't mean that as
disrespectful as it sounds,because it's good. But you're
not getting the flexibility ofbuilding your own shit, it's a
(39:15):
lot slower. And it's gonna takeyou a lot of time.
Pete Cuff (39:19):
So and you need to work out how to make it linked
to your Podio data, because it'snot built for poEdit. It's not
built for polio, it can talk topolio, but you need to make it
do it. Whereas a proc foo isbuilt to talk to polio, your
custom Ferrari isn't but theperson putting together would be
doing Podio integration for you.
Jordan Fleming (39:39):
And I think you if you're going to really think
about a use cases where sayyou've got customers and you
want them to log in and seeinformation in their orders or
their projects and, and be ableto give you updates and all that
but you don't want them in Podioyou've really got those two
pillars. It's either a proxymini app, or a custom web
(39:59):
application. My opinion and arereally the ways you want to
look. One is going to cost you alot less, but be less functional
and, and slightly less, youknow, design wise, you're gonna
have slight restrictions and allthat, but it's gonna be quicker
and cheaper. And one is going tobe where you really care about a
brand experience, etc. Andyou're building you're expecting
(40:21):
to spend 15 to $20,000 to builda web portal, like those, like,
to me, those are the only twothat matter in my opinion, what
do you think?
Pete Cuff (40:30):
Yeah, I completely agree. I think I think I want
bubble IO. And I like it to bemore Podio leaning than they
are, but they're not. So youknow, the strength that that
things like bubble might have isthat they are more suited also
say to dovetail straight intothe Google API and, and track
(40:51):
maps all over the place orintegrate to a payment gateway
or because again, that whatbubble? What bubble does is it
saying we're going to be yourown low code, no code, App
Builder service, you just linkit to what you want. And then
you can drag and drop this stuffaround. As I said, though, but
Podio isn't out of the box. Soit can't do that for Podio. It
(41:12):
doesn't.
Jordan Fleming (41:12):
Yeah, and I gotta say, I mean, we did a
project a couple years ago. Andyou know, that's a project we
did a couple years ago, usingbubble.io. And it may have
improved a lot. But it, itwasn't very, the problem is, and
particularly if you've beenused, so used to using Podio. If
(41:34):
you're really used to buildingin Podio, you used to being able
to do almost anything withCitrix. PWA like spoils us,
because you can do almostanything, add in proc foo and
fucking you can do anything. Anddo it quickly. And the problem
is when you that, that sets yourexpectations, that everywhere
(41:59):
else their workflow automationcan be done that quickly and
that brilliantly and bubblesimply wasn't there. It maybe it
is now maybe it is now but itjust wasn't there. And so we
ended up with I we ended up likefeeling like we were walking
through treacle, you know, likemolasses when you were trying to
(42:19):
do this. So really, I think yourbest options are proc food. I
think proc for many apps, if Iwas going to say to anyone who
wanted to get started onexternally externalising Podio
data right now proc foo.com.
Fucking buy an account and readup on many apps because I can I
and I don't build in Podioanymore, and I haven't built in
(42:44):
Podio. Really for three years, Ican still put together a mini
app in 20 minutes, which doeswhat I need it to do. It's not
gonna have lots of bells andwhistles, but it's that sort of
it's got the Podio do ityourself, feel. But your results
can be really quite nice.
Pete Cuff (43:05):
Yeah, agreed. And again, it is like all these all
these things, all the stuffwe're talking about. The more
you delve into it, the more youunpick it, the more you pull it
stuff, you'll find more and moreand more options, more and more
possibilities. But equally, thenthe more complicated, you're
making it. So it's more likelythat you're going to need to
learn some coding elements aswell in order to get the
(43:26):
absolute most out of it. Butyou're right, that it's in
various places. It's kind ofjust dropship, press this
button, and I think Andres hasreleased the ninja that can
build a mini app for you in like30 seconds.
Jordan Fleming (43:43):
Comparatively, if we're talking about you know,
I mean, you've got a Podioconsultancy, you build Podio for
people all the time. You know,you guys, I'm sure that, you
know, you can build the time ittakes to build a Podio miniapp
even one that's relativelycomplex, compared to the time it
(44:04):
takes to build a web applicationfrom scratch. Yeah, even if
you're using a symphony or, youknow, one of these kinds of
coding structures, even ifyou're using that the time, you
know, in eight to 10 hours of ofwork, you can get an enormous
amount done versus eight to 10hours in a web application is
(44:25):
like well, okay, we've gottenstarted this year, right and,
and so really like that's whatI'm saying it's I don't I don't
mean it to be disrespectful whenI say a Ford versus a Ferrari.
Because actually, you know, thatyou're all I'm talking about is
you know, it's more it's notabout Ford versus Frey so much
as it's, you know, one there arerestrictions, but the cost and
(44:48):
speed are a massive advantage.
The other costs and speed gomassively down but the results
are up. Unbelievable. So youwhere's your sweet spot? Do you
You need to spend $35,000,building a web application a
complex web application that isall singing, all dancing and is
exactly branded and above law,when probably not, if you know,
(45:09):
in which case, you know, fivegrand will get you a tremendous
amount and a miniapp stage.
Yeah,
Pete Cuff (45:17):
you could do that, you know, a miniapp is a great,
a great proof of concept, youcan get there on an iterate
quickly, you can get it to testout your processes and how it's
going to work in the back end.
And if you really decide thatyou want more power, more grunt,
more speed, more, whatever ismissing, then you could take
that mock up for want of abetter way of putting it and so
and give that to a developersaying make that but do it over
(45:39):
here?
Jordan Fleming (45:41):
Absolutely. All right. Well, listen, I think
that's a pretty good overview ofthe ways, I would sum this up by
saying, you know, if you simplyif you want to simply show
people a bit of data, anexternal link, or a, you know,
there, there are ways of doingthat, that are pretty easy. I
(46:04):
would say, only bring peopleinto Podio. If you're going to
seriously bring them into Podio.
If you're not going to seriouslybring them into Podio,
investigate one of these othersystems, other ways of doing it.
And if you're going to reallytry and externalise a lot of
data, the best option is a miniapp or a web portal, the miniapp
being much quicker and muchcheaper, with some more
restrictions, the web portalbeing all singing, all dancing,
(46:26):
and budget is your only limit.
Right? So I mean, start to thinkabout what you know, start, I
would say, start to think about,what does it mean to me to
externalise Podio data? Who do Iwant to see it? What do I want
them to see? How do I want themto interact with it? And if you
(46:50):
answer those questions, it'lllead you to the way and if
you've got any questions, justdrop Pete a line, I'm going to
drop his contact informationinto the podcast information,
drop PETA line, or head over towe are game changers.com, you
can fill in a Podio a partnerrequest, I've got a whole group
of partners in which Pete is oneof them, where I can match you
(47:12):
up. But Pete has a huge amountof knowledge in this. His
contact details will be in thepodcast information. So please
do drop them a line.
Pete Cuff (47:21):
Thank you very much.
Jordan Fleming (47:23):
I Pete I gotta go. My daughter has a recital
and I am not going to miss it.
So So yeah, and I'm also headingoff to Italy tomorrow.
Unknown (47:34):
So I'd like to some of us say,
Jordan Fleming (47:38):
Yeah, I'm going on holiday. So this, this will
come out in a couple of weeks.
Pete Cuff (47:42):
All right. Well, thanks very much, Sheldon, been
great to talk to you.
Jordan Fleming (47:45):
Thanks so much for joining us. And thank you
guys, for listening. Pleaseremember to Like share, click
things that you're supposed tocollect and make sure that you
spread the gospel of Podio viathe supercharged podcast.
Narrator (47:59):
You've been listening to another awesome episode of
supercharged with Jordan SamuelFleming don't forget to hit the
subscribe button on our YouTubechannel to be notified of new
podcast episodes Podiomasterclasses and in depth Podio
extension reviews if you'veenjoyed this podcast, please
give us a review on your podcastplayer to help support the show
Popular Podcasts
Crime Junkie
Does hearing about a true crime case always leave you scouring the internet for the truth behind the story? Dive into your next mystery with Crime Junkie. Every Monday, join your host Ashley Flowers as she unravels all the details of infamous and underreported true crime cases with her best friend Brit Prawat. From cold cases to missing persons and heroes in our community who seek justice, Crime Junkie is your destination for theories and stories you won’t hear anywhere else. Whether you're a seasoned true crime enthusiast or new to the genre, you'll find yourself on the edge of your seat awaiting a new episode every Monday. If you can never get enough true crime... Congratulations, you’ve found your people. Follow to join a community of Crime Junkies! Crime Junkie is presented by audiochuck Media Company.
24/7 News: The Latest
The latest news in 4 minutes updated every hour, every day.
Stuff You Should Know
If you've ever wanted to know about champagne, satanism, the Stonewall Uprising, chaos theory, LSD, El Nino, true crime and Rosa Parks, then look no further. Josh and Chuck have you covered.