Shift workers often receive information through several channels. A schedule may arrive as an image, overtime hours may remain in chat, and income rules may live in a separate spreadsheet. When something changes, correcting every copy becomes difficult. KADEE: Shift & Income explores a single Android workflow for shifts, overtime and income estimates, with configurable rules instead of one formula imposed on every workplace.
Begin with the work calendar
The primary record is what shift happened on each day, when it started and ended, and whether overtime or a special condition applied. Once that structure is clear, the app can calculate an estimate from recorded entries. Starting with a money total and reconstructing its source later makes it much harder to explain which day or shift changed the result.
Income rules need to be configurable and explainable
Shift allowances, overtime rates, holidays and time-rounding rules differ between workplaces. Formula components should therefore be stored separately from shift entries. When a rate changes, the interface should explain whether that change affects previous entries or only new ones. A summary should separate base amounts, overtime and additions rather than showing only one unexplained total.
The phrase “income estimate” defines an important boundary. An app calculation may exclude tax, social-security deductions, absence adjustments, bonuses or internal payroll rules. It should not replace a payslip or accounting record. Its job is to help a user understand the expected shape of a month and notice differences before comparing the result with official documents.
LAN sharing still requires trust decisions
Version 1.1.0 supports schedule sharing on a local network. This can exchange information without sending every record through a cloud service, but sharing a network does not make every device trustworthy. Device discovery, recipient confirmation and a preview of the data being transferred should remain clear. A recipient should be able to cancel before imported entries reach the main schedule.
Cases that deserve direct testing
- Shifts that cross midnight and overtime that follows a normal shift.
- Editing historical start or end times after a summary has been calculated.
- Months with different lengths and public holidays.
- A rate change in the middle of a month.
- The same data viewed on a phone and a tablet.
- Receiving the same LAN schedule twice without creating duplicate entries.
A useful interface answers two levels of question
The first question is “What shift do I work today?” and should be answered quickly. The second is “Where did this estimate come from?” and requires a path back to the relevant days, hours and rules. A dashboard alone can look polished but remain difficult to audit. A detailed table alone makes the month hard to understand. The product needs to connect each summary with its source records and keep edits understandable.
Where the product should go next
The current release supports phones and tablets. The highest-value next work is clearer formula explanations, duplicate detection and reliable backup, rather than producing estimates with more precision than the recorded evidence supports. The tool should reduce manual record keeping and make checking easier without presenting an estimate as a guaranteed payment amount.