StayRank is a complete Flutter source code package for a hotel recommendation app that ranks hotel alternatives with the MOORA method.
I built this project as a commercial-ready starter for developers, students, and makers who want a recommendation app that already has a working decision-support flow, local CSV data, clean separation of responsibilities, and a UI experience that can be customized without rebuilding the app from zero.
The source code is available through Gumroad and is prepared for study, customization, resale packaging, and long-term maintenance.
What you get
StayRank gives you a working Flutter project for hotel recommendation, not just a static UI template.
It includes hotel data loading, criteria weights, MOORA calculation, ranked recommendation output, Provider-based state management, centralized routing, shared formatting utilities, documentation, and bundled hotel artwork. The project keeps the original visual experience intact while cleaning up the architecture so the source package is easier to understand, edit, and deliver.
The package is useful if you want to:
- study a practical Flutter decision-support implementation
- build a hotel recommendation app without starting from a blank project
- learn how MOORA ranking can be packaged into a mobile product
- customize hotel alternatives and criteria from CSV files
- use a finished source package as a starting point for coursework, portfolio work, or a commercial template
- inspect a cleaner Flutter structure where screens do not own the ranking calculation
Core features
StayRank is built around hotel alternatives and measurable decision criteria.
- Hotel alternatives are initialized from CSV files under
assets/docs. - Criteria weights cover price, facilities, location, and star rating.
- Recommendation calculation uses MOORA normalization, preference weighting, and final ranking values.
- State management is handled with
provider. - Routing uses Flutter
Navigatorwith a centralized route registry. - US Dollar rate formatting is isolated in a shared utility.
- UI screens stay inside
presentation/screens. - Domain calculation logic is kept away from screen widgets.
- Hotel artwork is bundled locally under
assets/imagesas generated WebP images.
Because the active data lives in CSV files, the project is easier to adapt for a new hotel set, city, target user, or ranking case. You can adjust the alternatives and scoring fields without reshaping the whole app.
Why MOORA
MOORA works well for hotel recommendation because the decision is naturally multi-criteria. A user may care about price, facilities, location preference, and star rating at the same time. Some criteria should be maximized, while others should be minimized.
For buyers who need a source package that can be explained in a proposal, coursework, or technical presentation, MOORA is useful because the ranking process is visible and structured.
The hotel selection case can be represented with criteria like this:
| Code | Criterion | MOORA Type |
|---|---|---|
C1 |
Price | Cost |
C2 |
Facilities | Benefit |
C3 |
Location or distance | Cost or benefit, depending on data shape |
C4 |
Hotel class or star rating | Benefit |
C5 |
Preferred area match | Benefit |
The current StayRank dataset uses four active criteria:
| App Field | Criterion | MOORA Type |
|---|---|---|
price_score |
Price | Cost |
facility_score |
Facilities | Benefit |
location_score |
Location preference score | Benefit |
stars |
Star rating | Benefit |
Location is stored as a preference score in this app, so a higher value is better. If the project is changed to use physical distance in kilometers, location should be treated as a cost criterion instead.
MOORA formula
For hotel alternative i and criterion j, the normalized value is:
Normalization
xij = original value for hotel i on criterion j
xij* = normalized value after vector normalization
The weighted value is:
Preference Weighting
wj = weight for criterion j
vij = weighted normalized value for hotel i
The final MOORA score is calculated by subtracting cost criteria from benefit criteria:
Final MOORA Score
For the current StayRank implementation, the formula becomes:
Hotels are ranked from the highest Y_i value to the lowest value. The highest score becomes the strongest recommendation.
Built for customization
The source package is structured so the ranking logic and UI flow are easy to navigate.
lib/
app/ # MaterialApp composition and app routes
core/ # Models, theme, and shared utilities
data/ # Data sources and repositories
presentation/ # Providers and screens
main.dart # Entry point
assets/
docs/ # Active CSV data
images/ # Original generated WebP hotel images
docs/
INSTALLATION.md # Installation, customization, build, and release guide
CURRENT_STATES.md # Current implementation snapshot
DECISIONS.md # Important technical decisions
The active app reads hotel data through the data source layer from CSV files in assets/docs. Keep criterion labels aligned with:
pricefacilitieslocationstar
This makes StayRank easier to rebrand, expand, or adapt into another recommendation case that still depends on measurable alternatives and weighted criteria.
Who this source code is for
StayRank is suitable for:
- Flutter learners who want a complete recommendation app example
- students working on decision-support systems or MOORA method projects
- developers who need a hotel-ranking starter package
- portfolio builders who want to study multi-criteria recommendation logic
- makers who want to customize a source package for resale or delivery
It is especially useful when you need a project that demonstrates both product flow and ranking logic in one Flutter codebase.
What makes it different
StayRank is not only a hotel listing UI.
It includes a recommendation calculation workflow, weighted criteria, data loading, ranking output, local image assets, documentation, and a cleaner architecture that keeps domain logic away from presentation screens. That makes the source easier to explain, easier to maintain, and easier to adapt into a polished package.
The value is in the combination: a hotel recommendation product idea, a working Flutter app, and a decision-support method that can be described clearly in technical or academic material.
Availability
The source code package is available on Gumroad:
Review the Gumroad page and included documentation before adapting the project so the usage boundaries and package contents are clear.
License and usage
StayRank is distributed under a proprietary commercial license. Usage, resale, redistribution, modification, and warranty terms follow the included license.
Before selling or delivering a customized package, prepare a clean source archive that excludes build output, repository metadata, IDE settings, machine-specific Flutter or Android files, environment files, signing keys, logs, and temporary files.








