Skip to main contentSchylvaRequest a demo

School management apps for Indian schools

Your complete school day,
coming to iOS and Android.

Schylva is bringing its school management experience to iOS and Android for Indian schools. At launch, administrators, teachers, parents and students will carry their confirmed role workflows into a mobile-appropriate interface.

Book a mobile launch reviewExplore the four role journeys

Not currently available to download. Store links will appear only after the production listings are verified.

Availability and scope

The same role outcome.
A device-appropriate experience.

At launch, each confirmed school-role workflow will be available across web, iOS and Android. Mobile navigation and controls will adapt to the device without reducing the role to a companion viewer.

What complete means

  • Each role will retain its confirmed launch workflow
  • Navigation and controls will adapt for mobile interaction
  • Web and mobile will share workflow outcomes, not identical layouts

What it does not imply

  • Platform-owner Super Admin is outside the four-role mobile promise
  • Future, unfinished and excluded capabilities are outside this scope
  • Store availability will be stated only after production verification

This is planned launch scope, not a currently downloadable native build or a promise of an identical screen on every device.

Four roles. Four daily paths.

Start with the person.
Then follow the work.

Each brief pairs planned launch scope with a current web example. These are independent sample-data captures, not native app screens or a matched end-to-end school day.

Coordinate the school

School administrators

Planned at launch

At launch, move from the school overview to the operation that needs attention.

  1. StartSchool overview and operational context
  2. ChooseRelevant attendance, fee, timetable or exam workflow
  3. ActSupported record review or configuration
  4. ConfirmCorrect teacher, parent or student view

School context and daily operations

  • School overview, people, classes, sections, accounts and available permissions
  • Attendance, fee status, payment records, timetables and substitutions

Academics and coordination

  • Exams, results, circulars, holidays and supported school analytics
Review the school administrator workflow

Current web evidence · not a native app screen

Sample administrator web attendance analytics with a selected class, attendance summary and an attendance-not-submitted warning
Administrator web attendance analytics · static product screenshotEnlarge screenshot: Administrator web attendance analytics

Administrator web attendance analytics

Reviewed sample school data. Static image—product controls are not interactive.

A focused attendance-analytics view, not the complete dashboard or Results tab. The not-submitted warning remains visible; example percentages are not proof of complete or reconciled data.

Actual native role screenshots and verified workflow parity are still required before release.

Move through the teaching day

Teachers

Planned at launch

At launch, move from the timetable to the right class action.

  1. StartRelevant teaching schedule
  2. EnterAssigned class or subject context
  3. ActAttendance, homework or study-material workflow
  4. ConnectAppropriate administrator, parent or student record

Teaching context

  • Assigned schedules, classes, sections, subjects and daily attendance

Academic work and school updates

  • Homework, study materials, remarks and relevant exam information
  • Teacher-facing circulars and applicable notifications at launch
Explore the teacher mobile launch workflow

Current web evidence · not a native app screen

Teacher web assignment workspace showing Science, Class 6-A, an empty assignment list and the Assign Homework control
Teacher web assignment workspace · static product screenshotEnlarge screenshot: Teacher web assignment workspace

Teacher web assignment workspace

Reviewed sample school data. Static image—product controls are not interactive.

This assignment workspace is empty. It does not demonstrate daily attendance, a published assignment, a completed hand-in or Teacher review.

Actual native role screenshots and verified workflow parity are still required before release.

Keep each child in context

Parents

Planned at launch

At launch, keep every linked child and school action in context.

  1. Sign inConfigured parent account
  2. SelectCorrect linked child
  3. ReviewRelevant child-specific school record
  4. ActAcknowledgement or configured online-payment path

Child-specific school day

  • Multiple linked children, attendance, assignments, remarks, calendar and timetable
  • Published results, materials and circular acknowledgements

Fees and supported actions

  • Fee history and configured parent online payment through the supported school path
Explore the parent mobile launch workflow

Current web evidence · not a native app screen

Sample Parent web overview for August 2026 showing attendance on two marked days, no pending homework or remarks and sample fees due
Parent web child overview · static product screenshotEnlarge screenshot: Parent web child overview

Parent web child overview

Reviewed sample school data. Static image—product controls are not interactive.

August 2026 summary: 100% refers to only two marked days. The sample amount due is not a price, proof of payment availability or a completed transaction.

Actual native role screenshots and verified workflow parity are still required before release.

Find the current school day

Students

Planned at launch

At launch, find today’s timetable, work, updates and published records.

  1. Sign inConfigured student account
  2. StartRelevant school-day overview
  3. OpenTimetable, assignment, material or circular
  4. ReviewAttendance, remarks or published results

Academic day

  • Timetable, assignments and supported study materials
  • Calendar information and school circulars

Personal school record

  • Supported attendance, remarks and published results
Explore the student mobile launch workflow

Current web evidence · not a native app screen

Sample Student web published result with fictional 200 out of 200 marks, grade A plus and English and Mathematics subject rows
Student web published result · static product screenshotEnlarge screenshot: Student web published result

Student web published result

Reviewed sample school data. Static image—product controls are not interactive.

The fictional 100%, A+ and 200/200 are not school achievement claims. The Report card label does not prove a downloadable PDF or any native app functionality.

Actual native role screenshots and verified workflow parity are still required before release.

Connected product areas

Ten feature areas.
Always filtered by role.

Explore the approved mobile feature directory. A connected product area does not give every school role access to every action.

School foundation

Prepare the people, relationships and accounts behind each role.

At launch, each mobile role will use the supported school, person, class and account context from the connected platform.

Daily operations

Keep everyday school records connected to the relevant role.

At launch, attendance, fee status and schedules will follow the appropriate role context. Transport route and assignment records remain in the authorised administrator workflow.

Coordination and oversight

Publish the right update and review supported school summaries.

At launch, targeted communication will reach the applicable role while authorised administrators retain supported operational visibility.

Connected school updates

A useful update.
A relevant school record.

At launch, applicable in-app and push notifications will guide the correct role or audience to the related Schylva record. This is a planned path, not a delivery simulation.

  1. School action

    A supported school workflow will create or change a record.

  2. Applicable role or audience

    The update will follow the relevant school and role context.

  3. In-app or push update

    An applicable notification will guide the user into Schylva.

  4. Related Schylva record

    The user will reach the underlying school record where applicable.

Applicable launch coverage may include

  • Attendance
  • Circulars
  • Homework
  • Study materials
  • Exams
  • Results
  • Fees
  • Payment confirmations
  • Remarks
  • Timetable changes

Verification

Login verificationSMS delivery not current
Product-managed login-verification SMS requires implementation and release proof.

Device controls and delivery

Push controlsManaged in device settings
Users will retain the notification controls supplied by their device.
Push deliveryNot guaranteed
Delivery can depend on permissions, device state and external notification services.

Outside the current promise

WhatsAppNot supported
WhatsApp product messaging and alerts are outside the launch scope.
Non-login SMSNot supported
Operational SMS alerts are not a supported product channel.
Email alertsNot currently marketed
Email delivery and read tracking are not current public claims.
Optional in-app categoriesNot planned at launch
Custom in-app notification-category preferences are outside the launch scope.

Current web evidence · not a native app screen

The school prepares the record.

Empty school web circular form showing title, description, audience and optional attachment controls
School web circular preparation · static product screenshotEnlarge screenshot: School web circular preparation

School web circular preparation

Reviewed sample school data. Static image—product controls are not interactive.

An empty web form showing audience and attachment controls—not a sent circular or a delivered notification.

Inspect the communication workflow

Current web evidence · not a native app screen

The Parent finds the underlying update.

Sample Parent web circular awaiting acknowledgement with an Acknowledge control
Parent web circular acknowledgement · static product screenshotEnlarge screenshot: Parent web circular acknowledgement

Parent web circular acknowledgement

Reviewed sample school data. Static image—product controls are not interactive.

An independent historical circular awaiting acknowledgement. It does not prove push delivery, deep linking or completed acknowledgement.

Inspect the communication workflow

These captures are not the same circular. Native notification delivery, permission states and notification-to-record routing require separate release evidence.

Login and role context

The right account.
The right school context.

The planned path will begin with a configured school account relationship, use a release-approved verification method and continue into the relevant role workspace and record.

  1. Configured school account relationship

    The mobile path will use the administrator, teacher, parent or student relationship prepared by the school.

  2. Configured verification step

    The current web release accepts a configured six-digit code and does not send it by SMS. Mobile verification delivery requires release approval.

  3. Role-aware workspace

    The account will enter the focused experience for its configured school role.

  4. Relevant school, class, child or student record

    The user will reach only the supported context relevant to that school relationship.

From current web to verified mobile

Prepare deliberately.
Launch with the evidence.

Use three clear stages to prepare the school context, validate the mobile launch workflows and confirm release readiness.

Prepare mobile access as part of the school rollout.

  1. 01 · Prepare

    Set up representative accounts and relationships.

    Prepare the required administrator, teacher, parent and student accounts, including parent-child, class, subject and school-role relationships.

  2. 02 · Validate

    Review priority workflows and notification paths.

    Use representative records to review the school’s required role workflows, notification-to-record journeys and device permission states.

  3. 03 · Approve

    Complete training and confirm release readiness.

    Prepare relevant staff, confirm support expectations, record outstanding actions and keep store links inactive until the production listings and release evidence are verified.

Demonstrated now.
Confirmed before release.

Demonstrate now

Follow current web workflows with representative records.

  • Required school-role accounts and relationships
  • Current workflows that must carry into the mobile launch scope
  • The configured login-verification and parent payment paths when required

Validate for the school

Record workflow, permission and rollout requirements.

  • Priority notification-to-record journeys
  • Device permission, training and support expectations
  • Any required capability currently listed as excluded or unverified

Confirm before release

Verify the platform details that are not yet published.

  • Official App Store and Google Play readiness
  • Supported OS versions and phone or tablet scope
  • Offline, language or other currently unverified requirements

Questions before launch

Clear expectations.
Before the first download.

Availability, roles, payments and device requirements—with the current limits stated plainly.

Are the Schylva mobile apps available to download now?

No. The iOS and Android experiences are coming at launch. App Store and Google Play links will appear only after the production listings are live and verified.

Are the screenshots on this page from the mobile apps?

No. They are current Schylva web workflows using sample school data. They show the product context behind the mobile launch scope and are not presented as iOS or Android screenshots.

Will Schylva support both iOS and Android?

Yes. The confirmed role workflows for administrators, teachers, parents and students will be available on both iOS and Android at launch.

Which school roles are included at launch?

The mobile launch scope includes school administrators, teachers, parents and students. Platform-owner Super Admin is outside this four-role promise.

What does complete mobile scope mean?

It means each school role will complete its confirmed launch workflows using mobile-appropriate navigation and interaction. It does not imply every future feature, Super Admin access or an identical web and mobile interface.

Will mobile look identical to the web experience?

No. At launch, the confirmed workflow outcome will remain aligned while navigation, layout and controls adapt to the device.

How will administrators, teachers, parents and students get mobile access?

The school will prepare the relevant role accounts and relationships. At launch, users will sign in through a release-approved verification path and enter the role experience connected to their school account.

How will school updates reach users?

At launch, applicable school updates will use Schylva in-app and push notifications, guiding the correct audience to the related record where applicable. Push delivery cannot be guaranteed.

Does Schylva use WhatsApp or SMS for school updates?

No. WhatsApp and non-login SMS are not supported product channels. Product-managed login-verification SMS is not currently available; applicable school updates are planned through in-app and push notifications.

Can users disable optional notification categories?

Custom in-app category preferences are not planned at launch. Users will retain the notification controls provided through their iOS or Android device settings.

Can one parent account include multiple children?

Yes. The current parent experience supports moving between children linked through the appropriate school and family relationship, and that workflow will be part of the mobile launch scope.

Can parents pay school fees on mobile?

At launch, the parent experience will include the supported online-payment path when the school has configured it. Razorpay or another gateway’s transaction charges remain payable separately by the school under the provider’s terms.

Are the mobile experiences included in the introductory offer?

Yes. The confirmed iOS and Android school-role scope at launch is included for qualifying schools. The Pricing and Offer Terms pages define the activation, duration and commercial conditions.

Will Schylva work offline on mobile?

Offline mobile behaviour is not currently a public product promise. Any offline requirement should be recorded during the school’s evaluation and confirmed only after release verification.

Which iOS and Android versions, phones or tablets will be supported?

Minimum OS versions and phone or tablet scope are not yet published. They will be stated only after the production builds and device coverage are verified.

Will the mobile experience support multiple languages?

Mobile language support is not currently a public product claim. Schools should record any required language during evaluation so it can be confirmed against verified release scope.

Plan the mobile launch scope

Your school’s priorities.
A clear mobile launch brief.

Use current Schylva web workflows to review the mobile launch scope for each school role and identify what still needs confirmation. This is a launch-scope review, not a demonstration of a downloadable mobile build.

Book a mobile launch reviewGet a custom quote

Use fictional or redacted examples. Do not send live Student records, credentials or payment details.