When I tested Taximeter - Meter App, I approached it as a practical business tool rather than a novelty. Its purpose is simple: turn an Android or iOS phone into a working taximeter for recording a fare while a journey is in progress. That narrow focus is also its biggest strength. I did not have to learn a large dispatch platform or sort through unrelated booking tools before getting to the meter.
The app comes from Meter App Inc. and sits in the business category. It is free to install, rated for Everyone, and has built a strong audience with a 4.7 average from around 19 thousand ratings and over a million installs. Those figures do not replace hands-on testing, but they do suggest that the basic idea is useful to a lot of people: a phone can be a convenient backup or everyday fare calculator when a dedicated meter is unavailable.
My overall impression is that this is best for independent drivers, small operators, and anyone who needs a straightforward way to calculate a taxi-style charge. It is less suitable for someone expecting a complete fleet-management system, automated booking service, or accounting package. The distinction matters, because the app can make the fare-meter part of a journey easier, but it does not turn a phone into an entire transport business.
How the everyday meter workflow feels
The most sensible way to use the app is to prepare before the passenger gets in. I would open the meter, check the selected fare settings, and make sure the phone has enough battery and a stable position in the vehicle. Once the trip begins, the app can serve as the visible running calculation instead of forcing me to estimate the amount mentally or rely on a handwritten note.
That preparation habit is more important than it sounds. A meter app is only helpful when its starting conditions match the way you charge. If the wrong tariff or unit is selected, the screen may still look convincing while producing a fare that does not fit your local practice. I therefore treat the opening check as part of the trip, just like checking the vehicle display or confirming the passenger's destination.
A realistic use case is a self-employed driver who occasionally works outside a regular vehicle setup. Before leaving for the day, the driver can open the application, review the fare configuration, and keep the phone mounted where both driver and passenger can see it. At the end of the ride, the running amount provides a clear reference for the conversation about payment. That is more useful than using a generic calculator because the meter is designed around a journey rather than a single manual multiplication.
I also found that the app makes most sense when the phone is dedicated to the trip. Switching repeatedly between navigation, messages, and the meter creates unnecessary friction. If navigation is needed, I prefer setting the route first and then returning to the fare screen. The fewer interruptions there are, the less chance of accidentally stopping, resetting, or losing track of the active calculation.
There is a human side to this workflow as well. A passenger is more likely to trust a clearly displayed running fare than a driver who announces a number without showing how it developed. The app does not settle every disagreement, and it should not be treated as proof that a charge is legally correct, but it gives both sides a visible reference during the ride. That transparency is one of the strongest reasons to use it instead of a basic calculator.
What I would check before the first trip
Before relying on it during paid work, I would run a short test without a passenger. This is not about trying to force a particular result; it is about learning where the controls are and seeing how the fare behaves as the journey progresses. A few minutes spent becoming comfortable with the start and stop process can prevent fumbling while parked at a pickup point or at the destination.
I would also check whether the phone is receiving notifications that could cover the screen. A call or message is normal, but it can make a visible meter less convenient at exactly the wrong moment. Keeping the device in a stable mount, using a readable brightness level, and avoiding a cluttered home screen all help. These are simple habits, yet they make a bigger difference than installing a second calculator beside the app.
The app is free, which makes this trial easy for a new user. It also includes in-app purchases ranging from $0.99 to $99.00 per item, so I would look carefully at any purchase prompt before confirming it. Free installation is not the same as every possible capability being free, and a driver should decide whether an optional purchase fits the business need rather than buying automatically during a busy shift.
Settings that deserve attention
The most valuable settings are the ones that define how a fare is built. I would inspect the starting charge, distance-related behavior, time-related behavior, and any available fare choices before using the app professionally. I am deliberately treating these as configuration areas to verify on the device, not as a promise that every local tariff model is supported in exactly the same way.
This is where experienced use differs from simply opening the app and pressing start. A driver who works with more than one rate should make a repeatable pre-shift choice instead of changing settings in a hurry between rides. If the app presents multiple configurations, naming or arranging them in a memorable order can reduce mistakes. If it does not provide the exact structure required by a local authority or company, that is a clear signal to use it only as a supplementary calculator.
Another useful check is whether the fare should run during waiting time. Real journeys are not always continuous: traffic, passenger stops, loading, and temporary parking can change how a charge is calculated. I would decide in advance how those situations should be handled and then confirm that the selected configuration reflects that practice. The important point is not to improvise a different rule for every passenger.
I would keep a written reference for the rates I am supposed to use, especially if the app is operated by more than one driver. That reference can be as simple as a note kept with the vehicle documents. It gives me something to compare against when reviewing the app after an update or when setting up a replacement phone. A meter is only as reliable as the tariff choices behind it.
The current version is 8.38.337.7, and the app requires at least operating system version 9. I would still check the device before a working day, particularly if the phone is older or used as a dedicated spare. Compatibility is not the only concern: an aging battery, limited storage, or a screen that dims aggressively can make a perfectly functional application awkward in practice.
Repeatable patterns that save time
My preferred pattern is a three-step routine: prepare the fare before pickup, start only when the trip is genuinely underway, and stop immediately when the chargeable portion ends. Keeping those actions consistent is more valuable than trying to operate the app quickly. Speed comes from repetition, not from tapping randomly through menus.
For drivers who use the same vehicle every day, leaving the phone mount and charging cable in a fixed position can turn the app into a dependable part of the dashboard routine. I would open it before the first pickup, confirm the configuration, and avoid changing unrelated settings during the shift. At the end of the day, I would close out the active ride and return the phone to its charging spot.
A second pattern is useful for occasional users: keep the app as a backup rather than making it part of every trip. If a dedicated meter is already installed and approved for the vehicle, the phone application can remain available for checking a calculation or covering an equipment problem. This avoids creating two competing sources of truth while preserving the convenience of a spare.
There is also a practical communication habit I recommend. At the start of a ride, explain briefly that the fare is being calculated on the visible meter. At the end, give the passenger a moment to see the final amount before switching to another screen. This costs almost no time and makes the device feel like a transparent tool rather than a private calculation hidden in the driver's hand.
One non-obvious trade-off is screen visibility versus battery use. A bright screen is easier for a passenger to read, but keeping it bright for a long shift can consume power. I would use the lowest setting that remains clear in the vehicle and keep the phone connected to a reliable charger. If the device becomes hot or charging is unreliable, the meter should not be treated as the only record of the trip.
Another is the temptation to use the app while driving. I would set everything before moving and avoid touching the phone in traffic. The convenience of a digital meter does not justify distracted operation. If a change is needed, pull over safely or wait until the vehicle is stationary in an appropriate place.
Where the app reaches its limits
The biggest limitation is scope. Taximeter - Meter App handles the idea of a taxi meter, but it is not a replacement for dispatch software, customer booking, driver scheduling, payment processing, or full business bookkeeping. Someone who needs those functions will be better served by a broader transport platform, with this app used only if a separate meter is still useful.
I would also be cautious about treating the displayed amount as automatically compliant with local regulations. Taxi rules can depend on jurisdiction, vehicle licensing, printed receipts, visible notices, approved hardware, and specific tariff structures. A phone-based calculation may be convenient without being an officially accepted meter. Drivers should check their own obligations before making it the primary device for paid work.
The app is not the right choice for a company that needs centralized control over many vehicles. A fleet manager may need shared rate updates, ride histories, staff permissions, and reports that can be reviewed from one place. A single-phone meter does not naturally solve those organizational problems. For an individual operator, that simplicity can be welcome; for a growing fleet, it can become a weakness.
There is a similar limitation for drivers who need detailed records after every ride. I would not assume that a running fare automatically becomes a complete invoice, tax record, or customer receipt. If the business requires those documents, I would pair the meter with a separate approved process for recording payments and expenses. The app can calculate the journey while another tool handles the paperwork.
Navigation is another area where expectations should stay realistic. A meter and a map serve different purposes. I would use a navigation app for route guidance and this app for the fare calculation, switching between them only when the vehicle is safely stopped. Drivers who want one application to provide routing, booking, communication, payment, and metering may find this focused design too limited.
Who will get the most from it
I think the strongest audience is the independent driver who wants a simple meter without committing to a large subscription-based business system. It can also suit a small operator who needs a backup on a spare phone, a learner who wants to understand how a fare meter behaves, or someone who occasionally provides rides and needs a clearer alternative to mental arithmetic.
The Everyone age rating makes it broadly accessible from a content standpoint, although professional use still depends on the driver's responsibilities and local rules. The app's long presence, having been released on December 8, 2014, and its substantial install base make it feel less like an experimental utility and more like an established option in this narrow category.
I would skip it as a primary solution if the business depends on certified hardware, automatic receipts, integrated card payments, passenger accounts, or fleet reporting. I would also skip it if I could not verify that its available configuration matches the fare rules I am required to follow. In those cases, a dedicated approved meter or a complete transport-management service is the better investment, even if it is less convenient to set up.
Compared with a normal calculator, this app wins because it is organized around an ongoing ride and presents the fare in a way that is easier to explain. Compared with dedicated taxi hardware, it wins on portability and low entry cost but loses on purpose-built reliability, installation, and possible regulatory acceptance. Compared with a full driver platform, it is quicker to understand but far narrower. That is the honest position I would give a friend: choose it for the meter, not for an entire operation.
My final view after using it
I like the restraint of Taximeter - Meter App. It does not need to become a booking marketplace or a complicated business dashboard to be useful. When I prepare the settings, keep the phone visible, and follow the same start-and-stop routine, it provides a practical way to calculate and show a fare during a journey.
Its weaknesses are equally clear. A phone can run out of power, be interrupted, or fail to meet the standards expected of an official taxi meter. Configuration mistakes can also create problems if the driver assumes that a plausible-looking number must be correct. Those are not reasons to dismiss the app, but they are reasons to use it thoughtfully and keep a separate record or approved backup when the work demands one.
For a free business app with a focused purpose, I find it easy to recommend to occasional and independent users who understand that boundary. The 4.7 average and audience of over a million installs match my general impression that the basic concept works for many people, while the available in-app purchases mean I would review the purchase screen rather than assume every option is included.
My recommendation is simple: use it as a prepared, visible fare tool, not as a substitute for every part of a taxi business. If that is exactly what you need, its straightforward workflow can be more useful than a crowded alternative. If you need compliance documentation, fleet control, payment handling, or integrated dispatch, choose a specialized solution instead and let this app remain a backup rather than forcing it to do a job it was not designed to handle.
