HiveSuite & HiveReactKit Development Update: Profile UI Fixes & Scheduled Snaps

sagarkothari88(78)

Published in

HiveDevs

Words

1042

Reading

5 min

Listen to this post

~7 min

HiveSuite & HiveReactKit

HiveSuite & HiveReactKit — Profile UI & Build Fixes

Correct Native Hive Profile Detection

Profile detection has been corrected so native Hive users are no longer incorrectly treated as Web2 users.

Native Hive accounts now correctly receive the full Hive profile experience, including the appropriate profile functionality and account-specific UI.

This is particularly important now that HiveSuite supports multiple authentication types. The application needs to distinguish between native Hive, Web2, and Web3 identities before determining which profile components and capabilities should be displayed.

Correct Web2 & Web3 Identity UI

Web2 and Web3 accounts now correctly display their respective identity information and posting-limit indicators.

This ensures that users see account-specific information instead of a mixture of controls or indicators belonging to another authentication type.

The improvements provide clearer separation between:

Native Hive profiles
Web2 profiles
Web3 profiles

This makes the overall profile experience more predictable and easier to understand.

Composer Prop Cleanup

Duplicate isWeb2User JSX attributes were identified and removed from composer components.

This cleanup helps prevent conflicting prop values and reduces unnecessary duplication in the component structure.

It also makes the shared composer implementation cleaner and easier to maintain as Web2 and Web3-specific behavior continues to expand.

Replier Stability Fixes

Several issues affecting the Replier experience were also resolved.

The fixes included:

Missing isWeb3 property handling
Missing containerRef
React hook warnings
Unnecessary dependencies

These changes improve component stability and reduce development-time warnings while keeping the Replier functionality aligned with the latest Web2/Web3 account-aware architecture.

Profile & Composer Fixes

HiveSuite Profile and Composer Fixes

Scheduled Snap Publishing

One of the major additions in this development cycle is the introduction of scheduled Snap publishing.

The new system allows users to prepare a Snap in advance and have HiveSuite automatically publish it at the configured time.

The implementation spans both the hive-inbox backend and the HiveSuite frontend, creating an end-to-end scheduling workflow.

Backend — hive-inbox

Scheduled Snap Model

A dedicated Scheduled Snap model has been added to the backend.

This provides the data structure required to store scheduled publishing jobs and maintain their state until the configured publishing time.

A background worker has also been introduced to process these scheduled jobs and automatically publish Snaps when they become due.

Scheduled Snap APIs

The backend now provides APIs to manage scheduled Snaps throughout their lifecycle.

Supported operations include:

Schedule a Snap
List scheduled Snaps
Reschedule an existing Snap
Cancel a scheduled Snap

This gives the frontend everything required to provide a complete scheduling management experience.

Background Publishing Worker

The new background worker monitors scheduled jobs and automatically publishes eligible Snaps.

This means the user does not need to keep the HiveSuite interface open when a Snap is waiting to be published.

The backend takes responsibility for processing the scheduled job and executing the publishing workflow at the appropriate time.

On-Chain Posting Authority Verification

On-chain posting authority verification has been added specifically for hivesuite.app.

Before scheduled publishing can take place, the backend verifies that the required posting authority is correctly configured.

This provides an additional validation layer and helps ensure that scheduled content can be published securely and legitimately on behalf of the configured HiveSuite publishing account.

Snap Metadata Preservation

The scheduled publishing system preserves the complete publishing information required by Hive.

This includes:

Full jsonMetadata
Rewards
Beneficiaries
Snap-specific formatting

Preserving this information ensures that scheduled publishing does not simplify or lose important metadata compared with manually publishing the same content.

Scheduler Configuration

Dedicated scheduler account and posting-key configuration has also been added.

This provides the backend with the required configuration to process scheduled publishing jobs securely.

Scheduled Snap Backend

Scheduled Snap Backend & Worker

Frontend — HiveSuite

Snap Scheduling Service

HiveSuite now includes a dedicated Snap scheduling service with complete API integration.

The service connects the frontend scheduling interface with the new backend APIs and provides the necessary operations for creating and managing scheduled Snap jobs.

FeedComposer Scheduling

The FeedComposer has been updated with a dedicated Schedule button.

A clock icon has also been added to make the scheduling action easy to identify.

Users can now configure a Snap for future publication without leaving the normal composer workflow.

Schedule Preview

A schedule preview has been added to the composer experience.

This gives users a clear indication of the selected publishing schedule before confirming the scheduled Snap.

The preview helps reduce mistakes and makes the scheduling workflow more transparent.

Snap Scheduling in FeedComposer

HiveSuite Snap Scheduling in FeedComposer

One-Click Posting Authority Delegation

HiveSuite now provides a one-click authority delegation flow using:

Keychain
HiveAuth

This simplifies the process of granting the required posting authority for scheduled publishing.

Instead of requiring users to manually navigate through multiple account-management steps, the application can guide them through the delegation process directly from the scheduling experience.

This creates a smoother onboarding path for users who want to start using scheduled Snaps.

Posting Authority Delegation

One-Click Posting Authority Delegation

Unified Authority Checks

Authority verification has been unified across multiple scheduled publishing workflows.

The same authority-checking approach now applies to:

Snaps
Blogs
Videos

This creates a more consistent publishing architecture and reduces the possibility of different content types implementing authority validation in separate or incompatible ways.

The unified approach also provides a stronger foundation for expanding scheduled publishing to additional content types in the future.

My Scheduled — Unified Scheduled Content

The My Scheduled page has been updated to manage scheduled Snaps alongside other scheduled content.

Users can now access their scheduled Snap jobs from the same broader scheduling management experience.

This provides a centralized place to review and manage upcoming publications rather than requiring separate pages for different content types.

My Scheduled

My Scheduled Content Management

🚀 Powering the Hive Ecosystem

Continuously improving HiveReactKit with reusable components that make Hive applications richer and more responsive.
Building shared infrastructure for media rendering, translations, and smoother community navigation across the Hive ecosystem.
Contributing open-source enhancements that improve usability, consistency, and long-term maintainability for Hive frontends using HiveReactKit.