►
From YouTube: Adaptive Cards community call – August 2022
Description
In this month’s community call, get an overview of the React Native Adaptive Cards Renderer and on usage of the React Native adaptive card SDK in a Microsoft Viva Connections mobile app and in a Luis-based chatbot based app delivered by CEO & Founder – Vasanthakumar Sarpasayanam and his team at BigThinkCode. The community-supported ReactNative renderer for Adaptive Cards is maintained by BigThinkCode. There was a 10-minute Q&A covering a host of topics. This call was hosted by J.P. Roca (Microsoft) | @jpthepm. Recorded on August 11, 2022.
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365/community
A
Welcome
everyone
to
the
august
adaptive
cards
community
call.
Today
we
have
bassam
from
code
and
some
other
members
both
on
the
microsoft
side
and
on
his
team
at
big
think
code,
who
will
be
presenting
the
react
native
adaptive
card
render.
They
will
also
talk
about
some
interesting
uses
of
the
react
depth
card
render
in
the
viewer
connections
app,
and
then
we
can
hop
over
to
the
q
a
section
without
further
ado
with
sound.
You
can
go
ahead
and
start
sharing.
B
Good
morning,
everyone-
and
then
we
are
here
to
present
that
update
card
render
for
react
native,
and
we
are
here
to
share
our
experience.
We
are
victim
code.
We
will
share
our
experience,
how
picking
code
team
vented
and
then
created
adoptee
card
render
for
specifically
for
react
native
and
we
supported
multiple
mobile
platform.
B
So
the
agenda
for
the
today
call
will
be
a
quick
recap
about
that
optical
for
the
newcomers.
I
think
there
are
a
few
audience
from
france
and
places
who
are
joined.
We
will
give
a
quick
summary
about
that
picard
and
then
what
it
has
been
used
for
and
without
further
delay,
we'll
quickly
jump
into
the
reactionary
adapter
cart.
What
is
our
motivation
to
start
the
reactivity
adapter
card,
open
source
contribution
and
we'll
cover
some
of
the
implementation
details?
B
Okay,
where
we
stand
as
of
today
and
then
what
is
our
road
map?
And
then,
if
you
are
looking
to
contribute
into
the
depository,
if
you
are
an
open
source
developer,
and
then
you
want
to
contribute
we'll
also
give
direction
where
you
can
start
and
then
a
bit
more
into
the
reactivity
and
optical
and
finally,
we'll
end
up
the
session
with
q
and
a
okay,
pretty
sure
that
we'll
we'll
have
a
lot
of
time
for
the
q
ending
cool
before
we
deep
dive
directly
into
radar.
B
B
We
help
turn
big
idea
into
amazing
products
and
create
a
platform
help
customers
in
to
solve
the
scalability
issue,
security
issue
and
all
which
comes
along
with
the
product.
Okay,
our
focus
is
continuously
to
create
a
value
for
our
end
customer.
We
are
very
focused
on
creating
the
value
that
is
our
the
delivery.
B
Let's
quickly
jump
into
the
quick
recap
of
anaptika,
so
adaptic
card
has
most
of
you
guys
know
it
it's
a
it's
a
platform.
I
must
extemport
for
ui
want
to
create
ui
in
a
very
open
standard,
and
then
you
can
openly
exchange
between
different
services
between
different
apps.
You
can
adapt
my
ad
update.
B
When
you
share
a
content,
when
I
share
a
json
snippet
between
multiple
lab
the
adapter
card,
renderer
gives
a
way
a
common
way
to
render
in
your
application.
It
could
be
a
third
party
application
or
a
web
application
or
inside
any
of
the
microsoft
ecosystem
like
be
it
be
a
power
user
or
if
you
are
developing
a
lewis
bot
framework
right,
the
lewis,
the
output,
the
rich
output
itself
is
an
adaptive
card
format
or
you
want
to
integrate
with
third
party
application.
B
B
So
what
is
the
motivation
and
where?
Where
did
we
start?
Okay?
So
back
in
2018-19
time?
We
we
happen
to
work
with
one
of
our
client
who
want
to
integrate
that
optical,
which
is
a
which
is
basically
a
e-commerce
application,
and
then
they
want
to
integrate
according
to
and
create
a
chat,
chatbot,
basically,
okay.
During
that
time,
their
apps
are
into
multiple
packages.
Their
apps
are
developed
based
on
the
react
nature
as
well
as
android
native
ios,
and
it
is
a
multiple
package
and
then
go
to
the
next
library.
B
B
What
we
have
to
do
is
we
have
to
take
the
android
sdk
as
well
as
ios
sdk,
and
then
wrap
it
in
a
react
native
way,
write
a
wrapper
around
that,
and
then
we
have
to
integrate
with
the
react
native
as
well
as
android
and
ios,
and
we
have
to
maintain
all
the
three
packages
in
a
different
way.
That
was
a
little
cumbersome
and
by
doing
it
we
are
losing
all
the
react
native
advantage
right
because
react
net.
B
You
provide
a
common
way
to
maintain
the
code
and
then
in
one
place
you
can
change
and
then
it
will
reflect
in
all
the
mobile
platform.
So
we
thought
this
is
a
good
potential
for
us
to
write
the
react
native
adaptic
card
sdk,
and
then
we
started
okay.
So
these
are
the
gaps
which
we
thought.
Okay,
we
need
to
address
and
then
write
the
reaction
to
sdk
so
that
the
reactivity
com
community
take
the
advantage
of
the
reaction
usdk.
B
They
take
the
advantage
how
they
can
extend
a
particular
component
in
a
react
native
way
and
then
maintain
it
as
a
one
source
code
and
by
the
way
it
is
not
just
for
react
native.
You
can
actually
integrate
the
reactivity
sdk
into
your
android
application.
Ios
application,
in
fact,
into
a
windows
application,
which
is
a
experimental,
we'll
talk
more
about
in
the
coming
slide.
B
C
So
as
lesson
said
at
that
point
of
time
in
2018
we
did
not
have
a
react
native
renderer,
and
that
was
a
ask
in
the
community.
So
at
that
moment
there
were
very
few
react
native
applications
that
were
adopting
react
native
applications
itself
and
that
they
wanted
to
add
up.
So
us
is
basically
returning
cards
in
adaptive
cards,
so
any
react
native
applications
that
wanted
to
render
a
card
in
their
bot.
C
So
that
was
a
major
drawback
at
that
point
of
time,
and
it
was
not
much
customizable
on
the
extendability
as
well.
So,
for
example,
if
you
wanted
to
add
a
new
property
or
custom
property
specific
for
a
client
that
was
not
possible
at
the
time,
and
for
that,
you
will
have
to
have
both
ios
and
android
knowledge
to
implement
any
new
features.
So
that
was
not
very
straightforward
and
it
was
hard
to
maintain
as
well.
C
So
that
is
where
we
decided
to
develop
a
truly
react
native
renderer
to
solve
all
these
problems
and
the
major
points
that
we
thought,
while
developing
this
renderer
is
to
make
it
very
easy
to
install
within
very
few
steps
and
highly
configurable
and
use
all
the
powerful
rendering
mechanisms
of
react
native
and
easy
to
integrate
with
our
host
applications
and
configure
the
themes
etc
as
per
the
host
application
standards.
So
that
was
the
primary
adjective
for
us
to
implement
a
true
react
native
renderer.
C
So
our
architecture
is
pretty
simple
and
it
is
very
powerful
also.
So
if
you
see
the
model,
factory
is
the
core
of
our
renderer,
so
model
factory
is
where
we
pass.
All
the
components
from
the
payload
apply
all
the
theme,
configuration
and
custom
host
configuration
and
any
other
styles,
and
if
we
want
to
extend
or
add
new
components,
apart
from
the
components
supported
by
adaptive
card
schema,
everything
will
be
both
registered
and
passed
and
formulated
in
the
model
factory.
C
So,
basically
the
input
will
be
the
adaptive
card.
Payload
and
output
will
be
the
pure
component,
a
pure
reactant
to
component.
That
will
be
the
actual
card
itself.
So,
as
I
said,
we
wanted
to
have
a
very
straightforward
installation
and
easy
to
implement
in
minutes,
so
we
had
a
very
straightforward,
simple
implement
and
we
distributed
the
adaptive
card
renderer
in
a
as
an
npm
package.
You
can
install
through
npm
installer
yarn,
add,
and
there
is
no
fancy
packages
or
any
pod
files
or
any
other
components
for
android.
C
You
have
to
specifically
install
it,
is
purely
react
native,
so
just
import,
the
core
component,
the
root
component,
adaptive
card
and
all
the
properties
that
is
required
for
your
application
to
render
the
electric
card.
So,
as
you
see,
it
is
a
plain,
simple
react
native
component,
and
so
it
has
to
all
the
guidelines
of
react.
Nato
component
and
you
can
place
wherever
you
want,
not
only
in
a
chatbot,
it
can
be
in
any
dashboard
or
whatever
you
want
to.
C
You
can
use
it
as
a
regular
component,
so
the
main
key
features
apart
from
and
also
that
is
very
challenging
for
us
to
implement.
We
have
drafted
it
here
so,
apart
from
what
is
given
in
the
adaptive
schema
like
the
regular
components
like
text,
block,
image
or
container
container
set,
etc.
We
allow
our
renderer
allows
the
developer
to
add
their
own
component
into
the
renderer
and
display
that
as
part
of
the
card
for
example.
C
At
this
moment
we
do
not
have
a
rating
component
or,
for
example,
if
you
want
to
have
a
review
card
and
if
you
want
to
add
a
star
based
rating
systems,
that
is
not
possible
at
this
moment
with
adaptive
card
a
given
component
with
a
schema
right.
So
as
a
developer,
I
have
my
own
rating
component.
I
can
inject
that
as
a
custom
component
into
our
adaptive
card
registry,
and
I
can
add
my
own
custom
schema
into
the
existing
adaptive
card
schema
and
that
will
render
as
part
of
the
card
itself.
C
C
So
what
we
suggested
was
to
extend
the
image
component,
provide
their
own
implementation
that
will
pass
the
authorization
headers
to
that
particular
image
view,
and
that
will
be
replacing
the
actual
react
native
image
component
that,
instead
of
rendering
the
actual
react
native
component,
that
will
be
rendering
the
component
provided
by
the
developer
or
the
application
itself.
So
as
I
will
explain
how
that
can
be
done
in
coming
slides,
and
we
also
supported
our
data
binding
right
from
version
2.2.
Currently,
we
are
version
2.3
and
right
from
2.2.
C
We
are
supporting
data
binding,
so
it
adheres
to
all
the
templating
services,
templating
schema,
etc.
So
it
is
out
of
the
box
or
where,
if
you
provide
a
proper
binding
data
and
the
actual
data
itself,
it
binds,
and
it
provides
you
the
populated
adaptive
card
out
of
it
and
along
with
host
config.
We
also
support
something
called
a
theme
config,
so
host
config
is
something
that
is
specific
for
that
particular
application
host
and
like
the
padding
sizes
and
what
you
define
as
large
small
medium.
C
So
apart
from
that,
the
react
native
application
or
a
component
has
something
called
a
javascript
or
as
react
native
scales.
So,
for
example,
if
your
entire
application
is
in
particular
color
palette,
your
buttons
are
all
blue
or
green,
and
you
want
your
adaptive
card
buttons.
Also
to
add
to
the
same
format.
You
can
provide
a
theme
config.
That
is
a
mere
react
native
component
style
that
will
apply
to
all
the
components
of
all
the
buttons
or
any
input
in
your
adapter
card.
C
C
You
can
also
provide
a
different
team
configuration
for
different
platforms
so
for,
if
you
want
to
add
a
specific
color
for
a
button
in
android
in
a
different
way,
you
can
provide
a
different
color
for
ios
it
everything
is
plain
json
you
can
just
provide
it
and
it
will
render
it
out
of
the
box.
So
this
is
a
core
feature
accessibility,
but
this
is
one
of
the
challenging
features
that
we
implemented
and
we
are
continuing
to
implement.
So
we
recently
added
accessibility
support
to
our
enterer.
C
So,
apart
from
touch
base,
accessibility
and
talk
backs,
we
came
across
a
requirement
from
our
community
where
they
want
to
also
have
a
keyboard-based
accessibility.
For
example,
most
of
the
phone
applications
will
not
be
attached
to
a
keyboard
right,
so
there
are
specific
changes
that
need
to
be
done
on
the
renderer
to
support
a
bluetooth,
support
keyboard
to
navigate
across
the
component
and
read
it
out
for
supporting
accessibility
and
for
markdown.
We
implemented
this
as
an
initial
feature
itself.
C
At
that
point,
we
implemented
our
own
markdown,
rendering
engine
is
entirely
widgets
based
and
it
is
also
released
as
an
external
package
and
we
use
and
we
maintain
our
own
microphone
engine.
So
apart
from
this,
we
also
got
a
few
requests
related
to
running
the
renderer
on
a
react
native
windows
application.
So
this
is
experimental
and
specific
context
related
issues
that
were
happening
only
on
react
native
windows
and
we
added
fixes
and
support
for
those
particular
issues,
and
so
it
supports
yet
native
windows.
Also.
B
By
the
way,
it
is
one
of
the
microsoft
initiative
to
support
react
native
for
windows.
It's
a
windows
community.
I
think
it
is.
It
is
going
to
come
soon,
but
even
that
particular
effort
itself
is
experimental
and
we
are
able
to
play
around
that
and
then
we
are
able
to
use
our
sdk
to
render
in
windows
as
well
that
that
is
that
is,
has
been
pushed
into
one
of
the
branches.
Somebody
is
interested.
They
can
actually
look
into
it.
B
The
other
point
over
here
is
a
lot
of
lot
of,
for
example,
the
markdown
in
general,
the
other
engines,
the
essentially
capability
everything
we
have.
We
have
custom
developed
the
reason
being.
We
want
to
keep
this
sdk
as
lightweight
as
possible
because
it
is
going
to
be
part
of
the
other
third
party
app
right.
B
C
As
I
said
earlier,
sensibility
is
one
of
very
interesting
and
useful
features,
and
we
don't
want
to
have
a
very
complex
code
for
that.
It
is
a
single
api
where
you
can
register
a
custom
implementation
for
an
existing
adaptive
component,
or
you
can
also
provide
a
new
element
into
the
registry
and
render
it
as
part
of
the
part
of
the
call.
So
it
is
just
a
single
name
code.
You
just
need
to
implement
your
logic
to
render
a
custom
implementation
for
that.
So,
along
with
this
renderer,
we
also
have
developed
a
visualizer
application.
C
That
is,
it
is
part
of
our
repository
itself.
It
allows
the
developer
to
quickly
create
all
the
cards
and
render
and
see
how
it
renders
and
how
any
of
their
changes
reflect
on
multiple
cards,
and
we
also
have
a
test
suit
to
validate
any
new
changes
that
is
working
on
all
the
different
type
of
cards.
I'm
just
quickly
sharing
my
simulator
to
showcase
how
it
looks
so.
This
is
a
basically
just
and
we
have
bundled
a
lot
of
different
schemas
to
just
showcase
how
our
adapter
renders
it.
C
C
So
apart
from
this,
there
are
a
couple
of
applications
that
is,
that
has
incorporated
our
renderer
in
their
live
application.
So
one
of
those
is
a
microsoft.
Viva
connections
application.
I
have
zayd
from
microsoft
here
I
will
hand
over
to
him
to
demonstrate
or
go
through
the
viewer
connections.
Application
forward
using.
E
E
So
what
is
microsoft?
Viva
right?
So
microsoft?
Vivo
is
a
brand
new
employee
experiences
suite
of
products
which
is
built
to
support
employee
communications
organization,
knowledge,
learning,
company
resources
and
insights
and
daily
flow
of
work,
and
it
is
a
suite
of
products
and
what
the
image
that
we
see
on
the
screen
is
for
the
viva
connection,
mobile
application.
E
So
what
is
vivo
connections?
Mobile,
the
viva
connections?
Mobile,
is
a
gateway
into
the
company
culture
and
communications,
and
it
is
built
over
the
the
microsoft
teams
platform
and
if
you
look
at
the
images
that
are
here,
microsoft,
viva
connections
consists
of
three
tabs:
the
dashboard,
the
feed
and
the
resources.
E
The
dashboard
experience
is
powered
by
the
adaptive
cards
framework.
So
so,
as
I
mentioned,
like
the
dashboard
is
powered
by
the
adaptive
cards
platform
for
the
mobile
app.
We
have
integrated
react
native
adaptive
card.
Sdk
as
viva
connections,
mobile
is
on
teams
and
teams
is
there
on
both
android
and
ios.
It
was
one
of
the
easier
choices
to
go
with
the
react
native
adaptive
card
sdk.
E
We
have
been
partnering
with
the
big
thing
code
team
for
about
two
years
now
and
in
the
process
we
have
collaborated
on
more
than
100
features
and
bug
fixes.
We
have
released
about
more
than
15
sdk
releases
in
in
that
course
of
time
we
have
enabled
critical
dashboard
viewer
connections.
Dashboard
scenarios
with
the
help
of
big
thing
code
team,
as
praga,
was
mentioning
the
capabilities
of
theming
and
styling,
which
which
have
been
added
into
the
react
native
renderer
and
like
apart
from
that
by
use
of
the
extensibility
feature.
E
We
have
enabled
some
viva
connections
only
features
like
a
file,
upload
location,
authentication,
etc.
Also,
we
have
worked
together
on
platform.
Library
updates,
like
react
to
support
various
versions
daytime
picker.
These
are
all
the
components
that
are
present
in
the
adaptive
card.
We
have
over
the
course
of
time
improve
them
with
some
more
support
with
the
latest
versions
of
the
libraries.
E
Also,
we
have
together
worked
on
schema
alignment
for
containers,
column
sets,
etc.
Various
adaptive
card
elements
over
the
course
of
their
development
adapter
card
schema
has
also
evolved,
and
we
have
come
together
to
look
at
these
elements
and
make
sure
that
the
they
match
the
schema
that
is
available
for
the
adaptive
card
platform
and
as
prague,
was
mentioning
the
accessibility
enhancements
and
support.
We
have
done
multiple
of
them,
both
in
the
voice
based
and
keyboard,
based
support
for
access
accessibility.
E
Thank
you
yeah,
so
this
video
basically
demonstrates
what
viewer
connections
look
like.
So,
if
you
look
at
this
first
screen,
we
have
several
cards
that
are
present
on
the
screen.
All
of
these
cards
are
being
powered
by
adaptive
cards.
We
are,
we
are
able
to
lay
out
different
templates
of
weaver
connection
cards.
Some
of
them
are
like
white
cards.
Some
of
them
are
smaller
or
single
column
cards.
Some
of
them
have
images.
Some
of
them
are
text.
Heavy.
Some
of
them
have
buttons.
Some
of
them
don't
have
buttons.
E
I
think
this
just
shows
few
more
capabilities
that
is
available
on
the
vivo
connection,
so
this
one
shows
the
deep
licking
into
another
apps
as
well,
which
is
present
in
viewer
connections.
So
it's
not
just
adaptive
cards.
Your
connections
more
provides
much
more
capabilities.
I
think,
but
we
love
for,
for
this
particular
conversation,
we'll
limit
it
to
our
integration
and
our
interaction
with
the
adapter
cards.
I
think
we
can
move
back
to
the
slide
okay,
so
these
are
some
of
the
resources
for
viva
connections
and
people
who
are
more
interested
in
the
viva
connections.
E
B
So
the
next
use
case,
which
I
will
probably
talk
is
this
is
one
of
our
the
biggest
e-commerce
customer
where
who
want
to
build
a
chat
application,
basically
a
chat
application
to
reduce
all
the
customer
service
interactions,
and
then
they
want
to
enable
chat
based
shopping
experience.
Okay,
so
that
is
the
all
about
the
application.
B
So
we
have
integrated
the
adapter
card,
because
our
after
card
provides
a
very
rich
interface,
unlike
a
text
based
which
doesn't
capture
a
lot
of
information
right
with
integrating
the
adapter
card,
because
by
default,
luis
queues,
adapter
card
as
a
output.
So
when
we
are
able
to
integrate
the
adapter
card
react
native
sdk
into
it.
It
was
able
to
present
a
rich
information
and
then
it
was
reducing
a
90
percent.
B
For
example,
you
can
go
to
this
chatbot
and
then
say
that
reorder
my
last
order
or
reorder
my
shampoo,
or
something
like
that,
my
shoe,
which
you
you
have
previously
ordered
it
exactly
knows
the
contacts
from
the
louis
smart
framework
and
then
the
adapter
card
would
pop
up.
It
will
show
a
present
quick
card
information,
saying
that
is
this:
you
want
to
reorder
just
click,
yes,
and
then
it
will
reorder
for
you.
B
That
is
the
kind
of
experience
we
have
built
using
the
for
this
application,
and
without
that
update
card
integration,
it
would
not
appear
possible
okay.
So
these
are
a
couple
of
use
cases
and
we
have.
We
have
worked
with
multiple
clients
who
have
been
using
the
right
directory
card.
We
just
want
to
present
the
two
use
cases
which
are
considering
the
time
limit.
The
next
session
would
be
okay.
If
you
want
to
contribute,
you
are
a
reactivity
developer.
B
I'm
pretty
sure
that
there
are
a
few
developers
in
the
call
who
want
to
contribute
to
the
package.
How
do
you
do
it
based
on
your
integration,
if
something
has
been
found
as
a
bug
or
something
you
required,
for
example,
the
extensively
right
using
the
extensibility
feature,
we
have
supported
a
lot
for
a
different
customer
for
one
of
the
use
cases
which
prague
discussed
the
images
or
any
particular
component
which
required
authorization.
B
We
are
able
to
extend
the
component
and
then
pass
the
authorization
editor
as
part
of
the
component
itself
in
that
way
that
it
produced
a
different
package
or
a
different
worker
own,
and
then
it
works
as
a
one
package.
Okay,
so
such
any
any
complex
or
any
challenges
you
guys
face
you
can
submit.
We
are
here
to
help
you
or,
if
you
find
any
bugs,
you
can
definitely
file
it
as
part
of
the
open
source.
We
will
definitely
prioritize
and
then
our
do
it.
B
B
So
probably
you
can
be
part
of
the
reviewing
committee
and
then
you
can
help
us
review
the
code
and
then
submit
more
commands
or
you
can
review
the
project
board,
which
is
part
of
the
github
and
then
and
submit
some
of
the
features
which
you
are
looking
for
or
take
some
future
and
then
our
bug
and
then
I
said
yeah
we
have
very
active
community.
Probably
you
will
hear
or
hear
see
the
review
comments
within
a
week
and
then
we
are
that
active
and
then
within
a
week
you
you
can
see.
B
So
these
are
the
top
active
contributors,
currently
balaji
bake
and
ibrahim
myself
and
prague.
So
so
these
people
are
currently
continuing
and
then
contributing,
and
there
are
a
lot
of
other
people
who
submit
bugs
and
then
extend
their
arm
to
help
for
a
particular
features
as
part
of
their
development
or
integration.
Okay
and
by
the
way,
zlatan
teams
has
helped
a
lot
to
test
and
then
validate
a
lot
of
our
sdk
speeches
and
then
in
terms
of
accessibility.
B
A
B
Thank
you
and
thanks
for
having
here
again,
I
think
one
of
the
previous
community
calls
we
presented
about
picture
card,
which
is
our
other
contribution,
so
people
who
are
interested
can
look
into
it
and
then
it
is
already
recorded
video.
Is
there
as
part
of
the
community
call,
and
then
you
can
look
into
it.
If
any
queries,
you
guys
can
reach
to
me.
Yeah.
A
Absolutely
and
I've
tried
to
go
ahead
and
paste
every
link
that
was
mentioned
in
the
cloud
chat.
If
there
were
any
that
I
missed
please,
let
me
know
for
the
community
call
that
presented
pictocard.
If
I'm
not
mistaken,
that
was
the
november
2020
community
call.
I
have
a
link
from
youtube
that
I
can
share
on
that
as
soon
as
we're
done
with
the
q
a
section.
A
B
B
Yes,
so
there
are
already
multiple
third-party
apps
which
adopt
the
react.
Nature
sdk,
if
it
is
a
for
example,
chatbot
is
one
of
the
well
used
case
and
then,
if
our
app
is
designed
as
a
card
based
interface,
it
is
a
great
way
to
use
adapter
card
because
it
takes
it
up
the
rendering
and
then
you
drive
the
entire
ui.
Based
on
how
microsoft
viewer
connection
have
done
right.
B
You
drive
the
entire
ui
based
on
the
card
based
design
and
then
based
on
from
your
backend,
and
then
you
can
change
the
json
dynamically
and
then
you
can
get
rendered
at
the
front
end
very
easily.
So
there
are
a
lot
of
third-party
app
reactivity
application
has
taken
advantage
of.
We
have
worked
with
few
of
our
customers
who
are
into
fitness
or
showing
something
like
coupons
or
something
like
that,
and
then
the
one
advantage
is.
It
can
be
quickly.
B
Shareable
right,
you
can
share
it
with
a
multiple
app
and
multiple
platform
and
people
are
taking
into
social
media.
Basically,
for
example,
you
can
use
this
app
for
taking
a
review
or
for
a
particular
app,
and
then
you
can
share
that
review
into
particular
app
or
into
your
teams
app
or
in
you
can
share
it
via
outlook.
There
are
various
way
to
do
that.
A
This
allows
the
the
dev
process
to
speed
up
a
little
and
allows
users
to
take
advantage
of
things
like
a
rating
control,
for
example,
or
a
progress
bar
control.
If
that's
something
that
is
supported
and
allows
for
for
quicker
iteration,
because,
typically
for
adaptive
cards,
what
we
look
to
do
is
support
these
features
on
every
render
the
android
renderer
ios,
renderer,
javascript
and-
and
this
slows
down
the
development
process
a
little
bit.
So
it's
awesome
to
see
people
take
advantage
of
extensibility
to
provide
a
quicker
iteration
on
these
features.
B
A
Absolutely-
and
I
also
have
to
say
that
the
cards
that
are
produced
by
the
viva
connections
team-
they
are
amazing.
They
actually
joined
one
of
the
calls
in
the
past
to
show
off
some
of
the
really
cool
adaptive
card
jsons
that
they
created,
and
it's
amazing,
to
see
how
pretty
the
cards
can.
Look.
When
you
have
someone
that's
adept
in
using
the
the
technology
and
has
really
good
sense
for
how
the
ui
should
look
and
feel
for
for
the
customer.
A
D
Yeah
hi:
this
is
saurabh.
First
of
all,
great
work,
guys
big
thing
team.
I
think
this
render
will
be
very
useful
for
the
rest
of
the
community,
so
good
job
guys.
My
question
is
for
the
adaptive
cards
community
like
currently
for
outlook
actionable
message.
We
are
supporting
target
1.4
version.
I
guess
so.
Is
there
any
road
map
for
supporting
universal
actions
for
actionable
messages.
A
A
I
see,
sir,
are
you
familiar
with
the
adaptive
cards
repository
and
the
issues
page
on
there
yeah?
I
do
yes,
I
think
the
the
best
way
to
reach
this
and
find
the
solution
that
that's
able
to
help
you
and
your
team
out
would
be
to
go
ahead
and
open
up
an
issue.
We
have
contacts
on
the
outlook,
actionable
message
team
that
can
take
a
look
at
this
and
help
out.
I
do
remember
there
was
a
similar
issue
that
we
solved
not
too
long
ago.
That
was
very
related
to
this.
A
It
was
someone
that
was
using
action
that
executed
and
was
having
trouble,
rendering
the
card
correctly
on
outlook.
So
we
we
were
able
to
find
the
solution
and
the
the
best
way
for
us
to
to
get
all
the
details
and
understand
exactly
what's.
The
problem
would
be
through
the
issues
page
that
we
have
on
our
repository.
A
Here
you
can
find
the
links
to
everything
related
to
adaptive
cards,
our
github
repo,
our
our
roadmap,
more
information
on
templating
and
tool
samples,
and
even
some
of
our
blog
posts
can
also
be
found
on
made
with
cards
dot
io
if
you're
interested
in
learning
about
the
other
microsoft
365
developer.
Community
calls
here
are
links
and
cadences
for
each
one
of
those.
And
if
you
want
an
overall
view
of
all
of
this,
you
can
also
jump
into
aka.ms.m355.
A
Thank
you
so
much
everyone
for
joining
the
august
2022
adaptive
cards
community
column.
These
calls
are
hosted
every
second
thursday
of
the
month,
so
the
next
one
is
scheduled
for
september
8th.
So
I
hope
to
see
everyone
there
once
again.
Thank
you
so
much
fasant,
saeed
and
bragadish
for
for
sharing
this
demo
and
the
awesome
work
that
your
team
has
done
both
on
the
viva
connections
app
and
the
react
native
adaptive
card
render
it's
it's
awesome
to
see,
and
we
really
value
the
contributions
that
your
team
has
provided.