AbiFlow's redesign brief on 26 September started with a specific idea: “Dein Abi wächst.” Your progress toward the Abitur grows.
That is a better organizing idea than “make the dashboard more premium.” It connects the next learning goal, a focus session, the tree, and visible progress. It also gives the interface a useful test: does this screen help someone see what to do next?
The native redesign and Full implementation landed in the repository that day. The design brief explains the intended hierarchy; the implementation ledger records what was built. Neither, by itself, announces App Store availability.
The next exam deserves the strongest position
The overview direction puts the next learning goal or exam ahead of the smaller statistics. Subject, timing, progress, and a direct focus action should form one readable unit.
XP, streaks, and accumulated minutes are useful context, but they should not compete equally with the next decision. A student opening the app between tasks needs an answer faster than they need a wall of achievements.
The tree becomes more useful in that hierarchy. It can connect today's effort to longer-term growth without hiding the action behind an illustration.
Keep the product's own identity
The handoff preserves forest green, a cream base, restrained yellow XP accents, and the existing tree or learning world. The references contribute spacing and hierarchy, while the content remains school planning.
That distinction matters when using visual inspiration. An attractive fitness screen can teach a lesson about emphasis without contributing its metrics, photography, or navigation to a school app.
I want AbiFlow to become more recognizably itself as the design improves. A generic polished interface would be a weaker outcome.
The less glamorous screens belong in the redesign
The brief includes the plan, focus timer, ranking, Abitur calculator, onboarding, editors, settings, menus, and dialogs. It also carries historical school-service screens. The implementation ledger explicitly preserves the current manual planning boundary, so those older references do not establish a restored WebUntis integration.
Keeping that full inventory prevents a common redesign failure: five attractive main screens surrounded by forms that still belong to the previous product. It also protects existing capabilities. A quieter layout should make the information easier to read, rather than removing it to make the mockup simpler.
The same principle applies to accessibility. Large text needs room in the plan; the timer's actions need to stay reachable; reduced motion needs an intentional version of the growth feedback.
An iPad is another composition
The handoff explicitly asks for more than a stretched phone layout. Extra width can separate a plan from supporting information, improve statistics, and keep forms within a readable measure.
That is a native design problem. Navigation, sheets, and safe areas should feel natural on the device, even when the brand tokens are shared.
The part of this redesign I want to carry forward is its starting point. A coherent visual system helps, but the strongest hierarchy begins with a real user decision. For AbiFlow, that decision is the next goal and the focus session that moves it forward.