Non-interest MORTGAGE CALCULATOR banner

Non-interest MORTGAGE CALCULATOR

1 devlog
3h 55m 1s

I’ve been working on a project that’s really close to my heart: a simple, non-interest mortgage calculator built with Streamlit. My goal was to make ethical finance a bit more accessible by creating a tool that helps people figure out their repaym…

I’ve been working on a project that’s really close to my heart: a simple, non-interest mortgage calculator built with Streamlit. My goal was to make ethical finance a bit more accessible by creating a tool that helps people figure out their repayment plans without the complexity of interest. It’s been a great exercise in building something practical that genuinely helps people make clearer financial decisions

Demo Repository

Loading README...

ABDULLAH QAMARDEEN

The Development Journey: Non-Interest Mortgage Calculator

A PHASE OF DISCOVERY
I started by searching for a Python library that could facilitate web-based applications. My goal was to find a tool that was both efficient and developer-friendly. That search led me directly to Streamlit. Once I saw how intuitive it was, I wanted to put it to the test with a meaningful project.

OUTCOME
I decided to build a non-interest (ethical) mortgage calculator. My logic was that while most financial tools are built for traditional interest-based models, there is a clear demand for alternatives—just like the existence of non-interest banks. I wanted to build something that was both technically sound and genuinely useful for users who prefer an ethical financial approach.

ENCOUNTERING AN HURDLE
The most challenging part of the implementation was the repayment schedule. Early on, the app was unresponsive—it was hanging instead of rendering the results.

SCALING THROUGH IT
After digging through the code, I realized I had made a logical error: I was iterating through a static list of currency rather than the dynamic year/month variables. It was a classic “missing the forest for the trees” moment. I went back to my resources and re-watched the core documentation, which helped me identify the misplaced variable. Fixing it was a huge breakthrough, and it taught me a lot about how Streamlit handles data loops and UI responsiveness.

Next Steps
The app is functional, but it’s still at the bottom of my task list for further refinement. I’m planning to:

Add visual elements (interactive charts) to better represent the payment journey.

Optimize the UI for an even smoother user experience.

Continue exploring Streamlit’s advanced features as I iterate on the design.

Attachment
0