Your comments

Hi Jamie,
I tried this out, and it should work if you chain the two behaviors. First, the PlayAudio should happen when the condition is true, and the Blink behavior can be chained after it, without a condition. The two should happen at the same time, because when something is chained to happen after a PlayAudio behavior it does not wait for the audio to finish.
Hi Charmaine,
We're planning to add the new categories in a future update of InteractBuilder, but if you submit your app before that update, you can email us to specify the primary and secondary categories you'd like to use for the app.
We're hoping to make the Marketplace available in the next two to three months.

Yes, we offer what we call our "studio services," where we can build your app, and this is priced depending on the amount of detail the project would require.

If you'd like to learn more about this, you can email me at inna@interactstudios.com. You could email me an overview of the project and how much artwork you have, and we can send you an estimate of the cost and amount of time.
Hi Charmaine,
When an app has an update published, then the app marketplace notifies the user that an update is available to download, both in Apple's App Store and in Google Play. We currently don't have the option to create custom push notifications for the app.
You're welcome! Glad we could help!
If it needs to become visible as well, then I would recommend putting the condition on the Show behavior instead and then chaining the animation behavior to happen after the Show behavior, like this:

(none)
Show
(Self)
Condition: Counter is 6

behavior after:
(none)
Animate
(Self)
Condition: (none)
Hi Jamie,
So actually you don't need the condition on the intersection but on the animation behavior. A condition tells the builder, "perform this behavior only if this condition is true." So the animation element can have the following action set:
Interaction: (none)
Behavior: Animate
Target: (Self)
Condition: {Page Counter} is {Value}
Element: Counter
Value: 6
Hi Jamie,
That looks like a great activity! Here's a technique I find helpful when creating this type of effect:

Since the image needs to be small and movable at one point and large and not movable at another point, create two separate elements for each puzzle piece.

The large pieces should be in their final places on the page (overlapping the white silhouettes), contain no action sets, and be invisible at runtime.

The small pieces should have two action sets (as well as any other effects you want to include):
- Drag-Move (Self)
- DragEnd-Move (Self) with a target location that matches the element's original coordinates.

Then for each piece you would create a set of intersections.
When the small image intersects with the correct silhouette at its center,
- Hide the small image
- Show the large image

With the intersections, you can also play sound effects or add to a counter if something should happen when all of the pieces have been placed.
Oh sorry about that! It looks like that behavior is being repaired and isn't available at this point.
Hi Jamie!
Here's a sample app that uses a color palette and drawing and erasing behaviors:

Drawing Sample

You can also check out all of the available drawing and erasing behaviors here

Drawing Behaviors.