An About screen can offer profile destinations without storing custom launch URLs in each widget. DeeplinkX supplies typed actions; the application supplies the real destinations and labels.
Reusable Flutter example
import 'package:deeplink_x/deeplink_x.dart';
Future<bool> openTelegramProfile() {
return DeeplinkX().launchAction(
Telegram.openProfile(username: 'durov'),
);
}
Future<bool> openInstagramProfile() {
return DeeplinkX().launchAction(
Instagram.openProfile(username: 'instagram'),
);
}
Future<bool> openLinkedInProfile() {
return DeeplinkX().launchAction(
LinkedIn.openProfile(profileId: 'satyanadella'),
);
}
These are the example app's public demo profiles. They are not official DeeplinkX support accounts. Replace them with your own accounts before presenting this as a product support page.
Current example behavior
AboutSupportPage shows three fixed social rows. Each row calls launchAction with its respective action. fallbackToStore defaults to false, so these examples do not opt into a store redirect. If native handoff fails, normal fallback behavior can try the action's documented web URL.
The screen prevents duplicate launches while a request is pending and shows the package's final Boolean as “Launch request succeeded” or “Nothing could be launched.” Those messages describe the handoff, not confirmation that a particular profile loaded.
Configuration and limits
- Add only the required provider packages and schemes to the integrating app's platform configuration. Compare Android visibility declarations and iOS query schemes.
- See the Telegram guide, Instagram guide, and LinkedIn guide for provider-specific configuration and URL behavior.
- Authentication, account existence, privacy, and profile availability remain provider concerns.
- Browser fallback opens the destination without requiring a native installation.
UI behavior
- Each row constructs the shown API with the correct identifier and default
fallbackToStore: false. - Demonstrate installed and unavailable native-app states without changing the profile identifier.
- Exercise failure and successful handoff feedback, and ignore duplicate requests while one is pending.