Skip to main content
The ChannelRepository provides comprehensive channel creation capabilities supporting Community, Live, and Conversation channel types. Each type offers unique characteristics and can be customized with metadata, tags, and specific configurations to match your communication needs.

​
Channel Creation Approaches

social.plus Chat SDK offers two standard methods for creating channels, giving you flexibility in ID management:

Custom Channel ID

Specify your own unique identifier
  • Full control over channel naming
  • Useful for integration with existing systems
  • Must ensure uniqueness to avoid conflicts

Auto-Generated ID

Let the SDK generate unique identifiers
  • Automatic conflict prevention
  • Simplified creation process
  • Recommended for most use cases
Conflict Prevention: If you attempt to create a channel with an ID that already exists, the API will return a conflict error (400900). When the channel ID parameter is undefined, the SDK automatically generates a unique ID to prevent conflicts.

​
Channel Types

  • Community Channels
  • Live Channels
  • Conversation Channels
  • Broadcast Channels
Public channels discoverable by all usersCreate community channels for open discussions, team collaboration, and public forums.

​
Parameters

ParameterTypeRequiredDescription
displayNameString✅Public display name of the channel
avatarFileIdString❌Image file ID for channel avatar
metadataObject❌Custom fields for extended functionality
tagsArray❌Searchable tags for channel discovery
isPublicBoolean❌Visibility setting (public/private community)

​
Code Examples

do {
    let builder = AmityCommunityChannelBuilder()
    // Optional. If you don't provide channel id, sdk will create a unique channel id for you.
    builder.setUserIds(["steve", "john"])
    builder.setDisplayName("My Community Channel")
    builder.setTags(["ch-comm", "ios-sdk"])
    builder.setMetadata(["sdk_type": "ios"])
    // Create a channel by passing the builder
    let channel = try await channelRepository.createChannel(with: builder)
    print("A channel is created: \(channel.channelId)")
} catch {
    print("Unable to create a channel: \(error)")
}

​
Best Practices

Strategic Considerations
  • Choose the Right Type: Match channel type to your specific communication needs
  • Plan for Growth: Consider how your channels will scale with user adoption
  • Metadata Strategy: Use metadata fields for future extensibility and custom features
  • Naming Conventions: Establish consistent naming patterns for better organization
Common Patterns
  • Use Community channels for open discussions and team collaboration
  • Implement Live channels for time-limited events and special conversations
  • Deploy Conversation channels for private messaging and support
  • Reserve Broadcast channels for official announcements and marketing
Robust Error Management
  • Conflict Handling: Implement proper handling for channel ID conflicts (400900)
  • Validation: Validate required parameters before attempting creation
  • User Feedback: Provide clear error messages for failed channel creation
  • Retry Logic: Implement appropriate retry mechanisms for transient failures
Common Error Scenarios
  • Duplicate channel IDs when using custom identifiers
  • Invalid or missing required parameters
  • Network connectivity issues during creation
  • Permission errors for restricted channel types
Efficient Implementation
  • ID Generation: Use auto-generated IDs unless you have specific requirements
  • Resource Management: Monitor memory usage when creating many channels
Optimization Tips
  • Leverage SDK’s automatic ID generation for better performance
  • Implement proper cleanup for unused or temporary channels
  • Monitor channel creation patterns and optimize based on usage

​
Next Steps

Manage Channels

Update channel properties and configurations

Query Channels

Search and filter channels effectively

Member Management

Add and manage channel members
Development Tip: Start with Community channels for general use cases, then implement specialized channel types as your requirements become more specific. The SDK’s automatic ID generation is recommended for most scenarios unless you need specific integration patterns.