Quicken 2007 Mac 64-bit Rebuild

@tangramua

Hello,   We carefully studied the description of your project and we can confirm that we understand your needs and are also interested in your project. Our team has the necessary resources to start your project as soon as possible and complete it in a very short time.   We are 25 years in this business and our technical specialists have strong experience in Software Architecture, Cocoa, Objective C, Software Testing, Software Development, Swift, Cocoa Touch and other technologies relevant to your project.   Please, review our profile https://www.freelancer.com/u/tangramua where you can find detailed information about our company, our portfolio, and the client's recent reviews.   Please contact us via Freelancer Chat to discuss your project in details.   Best regards, Sales department Tangram Canada Inc.     

@ahmadayaz

I understand the need to develop a 64-bit financial software application for macOS 13 and above, similar to Quicken 2007 but with upgraded features. My expertise in macOS development using Swift and Cocoa, coupled with experience in finance software, makes me well-suited for this project. I propose creating a modern, notarized universal-binary macOS application that replicates Quicken 2007's functionalities while enhancing the UI for a better user experience. Data security during import will be a priority to ensure a seamless transition without data loss. I will follow a structured development approach with alpha and beta releases for testing and feedback. Deliverables will include the application, detailed documentation, a user guide, and thorough testing. I am confident in my ability to deliver a quality product and look forward to discussing this project in more detail. Thank you for considering my proposal.

@sufyanasmat38

Hi Michael, we can build a native 64-bit macOS application that recreates the core Quicken 2007 workflows while keeping your financial data local and private. We can implement registers, Quickfill, QuickMath, categories, reporting, bill payments, and a reliable migration path for your existing data, with a modern Cocoa-based interface. We can work milestone-by-milestone, starting with registers and Quickfill, then reporting and bill pay.

@maxscender

The core challenge isn’t rebuilding the interface—it’s preserving the exact data semantics and interaction patterns that make Quicken 2007 feel right, while making it a modern 64-bit macOS app. I’ll start by analyzing your sample .QDF file to map its structure, then build a native Swift/Cocoa app around that data model. The first milestone will deliver a working register with Quickfill, categories, and QuickMath so you can validate split transactions and sales-tax behavior immediately. The second milestone adds reporting and bill payment, with the Spending by Category report matched against your original totals. The final app will be a notarised universal binary that runs on macOS 13 and later without Rosetta, and I’ll include full source and a short guide covering any unavoidable UI differences. My focus is on making sure nothing from your existing data is lost and that every critical workflow—especially Quickfill, QuickMath, and reporting—behaves exactly like the original.

@Walkingdreams

As a seasoned professional with over 13 years of experience in software development, I am confident in my ability to not only successfully rebuild Quicken 2007, but modernize it as well. My expertise extends to various platforms, which includes a deep understanding of macOS systems and their compatibility nuances. This makes me the ideal candidate for delivering a ground-up, notarized, universal-binary macOS 13+ app that runs natively. Having delivered over 300 projects with a staggering 99% positive review record, I am well-versed in the importance of clear communication,strong code and predictable delivery. These qualities will be heavily relied on during our journey as we seek to replicate each feature you hold dear in Quicken 2007; functionalities like bill payment management, detailed reporting and Quickfill autocomplete are no small feat,but they are precisely the sort of tasks my team and I have a proven record of taking in stride. Lastly, importation of your existing financial data without loss is an aspect that I take seriously. I understand the need to retain one's financial history securely hence my explicit commitment to building an equally simple and seamless migration path. I invite you to leverage on my expertise not only for this task but also for any future support or Phase‑2 development that may arise. With me leading your project, you'll gain a partner who will be available for direct collaboration

@mayr81

Your Quicken 2007 rebuild is a strong candidate for a staged, reliability-first macOS application. The critical path should begin with a native 64-bit Swift/Cocoa foundation, a carefully designed data model, and deterministic migration from the supplied QDF sample so financial history remains trustworthy. I would structure the alpha around registers, split transactions, categories, QuickMath, and Quickfill, with automated regression tests comparing imported data and calculated balances against Quicken 2007. The beta would add the reporting engine and bill-payment workflows, including the Spending by Category report and scheduled-payment acceptance scenarios you specified. The application can use modern Cocoa accessibility and visual improvements while preserving familiar navigation and keyboard-driven workflows. Security should be treated as a core requirement: local-first storage, no unnecessary online integrations, transparent file handling, and signed/notarised universal builds for macOS 13+. You would receive the complete source, reproducible build instructions, milestone builds for hands-on validation, and a concise guide documenting intentional UI differences. The supplied screenshots, sample file, and acceptance cases can become the foundation for an executable specification and dependable long-term maintenance.

@melopgabriel

Hi Michael, You need a native macOS replacement for Quicken 2007 that preserves the familiar workflow while rebuilding the core financial tools people actually rely on: registers, importing existing data, QuickMath, Quickfill, categories, reporting, and bill pay. I understand the priority is not a generic finance app, but a trustworthy desktop product that feels close to the original and protects financial data. I have built desktop software with Swift, Objective-C, and Cocoa, including data-heavy interfaces where accuracy and usability matter. For this kind of rebuild, I would start with the data model and import path, then implement the register, Quickfill, and reporting engine behind a clean modern macOS interface. That keeps the first stable build focused on the features you marked as mission-critical. If you’d like, I can outline a practical milestone plan for alpha and beta. Best regards, Gabriel

@UzeeTech

Hello Michael, I can rebuild this as a secure, native 64-bit macOS app with a staged alpha/beta plan, preserving Quicken’s register-first workflow while modernizing Cocoa accessibility. I have 9 years’ full-stack experience with React.js, Node.js, Python, Flutter and AI/ML; for this project I’ll apply that architecture and testing discipline to Swift/Objective-C/Cocoa, local-first financial data and notarized delivery. • Safe .QDF import/migration with validation and backup • Registers, split transactions, QuickMath sales tax, Quickfill and categories • Bill-payment scheduling and classic Spending by Category/reporting • Universal binary, source/build instructions and acceptance tests against your sample file I’ll keep financial data local unless explicitly required and use milestones for alpha (registers/Quickfill) and beta (reports/bill pay). Could you provide the sample .QDF and confirm whether payment scheduling is reminders only or needs bank integration? Regards, Jaimish

@PINESCRIPTERR

Hi Michael, I understand you want a ground-up, native 64-bit macOS replacement for Quicken 2007 that preserves the familiar workflows while keeping your financial data local and private. I can build this as a native Swift/AppKit application for macOS 13+, with a clean separation between the financial data model, QDF migration/import layer and UI. The priority would be registers, Quickfill, bill-payment management and reporting, while preserving familiar Quicken-style navigation and workflows. For the data layer, I would first analyse your sample QDF file and determine the safest migration approach. The application can use a local database and operate without cloud services or online financial integrations. Financial calculations, split transactions, QuickMath, categories and report totals can be validated against the original Quicken behaviour using your supplied data. The final application can be delivered as a signed/notarised universal binary for Apple Silicon and Intel, with full source code, build instructions and a concise migration/user guide. I’ll also validate the acceptance workflow: importing the sample data, entering split transactions with QuickMath, scheduling payments and reproducing Spending by Category totals. Best regards, Houssame

@cliftonc20

Hi, Rebuilding Quicken 2007 as a modern 64-bit macOS app involves carefully replicating legacy workflows while integrating updated Cocoa UI components. The main technical risk is ensuring data consistency and seamless import from existing .QDF files without loss or corruption. My background is primarily in AI-driven backend systems rather than native macOS app development, so while I understand the importance of reliable data handling and user workflow preservation, this project’s core platform and UI stack fall outside my direct experience. I would recommend structuring the system to separate core financial logic and data import layers from the UI to allow iterative validation and testing of critical features like QuickMath and bill payment scheduling. Ensuring robust testing for data migration and transaction accuracy will be essential to maintain user trust and software reliability. If helpful, I can start by reviewing the data import strategy or mapping out the transaction processing flow to identify potential pitfalls early. Clifton

@HamparProd

The first milestone should prove your existing Quicken data can be migrated safely before rebuilding the rest of the application around assumptions. I would build this as a native Swift macOS application with local-only financial storage, deterministic decimal calculations and no cloud dependency. The core model would cover accounts, transactions, splits, categories, payees and scheduled payments, with registers and QuickFill built directly on that structured data. One item I would verify immediately is the source file format. Quicken Mac 2007 normally uses .QDFM, so I would inspect your actual sample file and prove the importer before committing the later reporting/bill-pay milestones. The final app can be delivered as a signed/notarized universal binary for Intel and Apple silicon, with source and build instructions. Rate: $45/hour. Initial milestone: 40 hours over 7 working days. I can start immediately after award with the sample data file, screenshots and expected report examples.