Skip to main content
Before your agent writes code, choose how much of the experience your app needs to own. Vise can inspect your project and recommend a path, but you make the final product decision.

​
Ask your agent for a recommendation

​
Compare the two paths

Choose UIKit when the desired experience is close to a standard social surface and speed matters most. Choose a custom SDK UI when the interaction itself differentiates your product or must fit an established app-specific workflow.
A mixed approach is possible, but it should be an explicit architecture decision. Do not start with UIKit and quietly replace standard behavior with raw SDK calls during implementation.

​
Decisions to make before implementation

Whichever path you choose, expect your agent to confirm:
  • the feature and capabilities that are in scope
  • the screen or route where it belongs
  • the social.plus region and identity source
  • where the feed, community, channel, or other target comes from
  • the design constraints and runtime environment the finished work must satisfy
Once those decisions are clear, ask the agent to record the agreed outcome and begin implementation.

​
Continue with your chosen path

Launch a standard social experience

Use a prebuilt UIKit surface with the lightest customization that fits.

Build a custom social experience

Build a differentiated, app-owned experience directly on the SDK.