Loading...
Answers
MenuHow difficult is it (in terms of programming) for a mobile app to track a user's mileage without displaying a map?
Would this use a large amount of mobile data?
Would having this running in the background use as much battery power as say Google maps (without ever having to display a map)?
Note:It's okay if the app is measuring in intervals (every 1/8 mile) if that would help reduce the data or battery useage...
Answers
Assuming you are looking for software, not in-car telematics, and you are willing to integrate rather than build it yourself, you could try using ZenDrive. That would give you a lot more than mileage too (eg, driving behavior).
This should neither use a large amount of mobile data nor use as much battery as Gmaps. Can't speak for iOS but this is what the Android documentation below has to say on location strategies and what it boils down to is that you need to determine how much accuracy your app needs, pick your strategy and maybe implement it as a background service that talks to your app. Someone who coded for Android before should have a prototype up and running within a few days. I assume however that this involves extensive testing on various devices and OS versions (the tricky part of mobile development).
http://developer.android.com/guide/topics/location/strategies.html
Yep, you would be polling intervals/speed and saving those locally during a drive session then you would post those numbers back to the server for calculation. No need to show a map.
Related Questions
-
What is the best programming language for building multi-platform mobile software that is scalable?
I've been involved in several projects that hinged upon this question (generally start-ups or web+mobile apps), and it's not a clean or easy answer unfortunately! Plus every developer you talk to is going to try to sell you their services, but what you need is simply the truth! I'd suggest that you consider shifting your focus away from finding a best language. That sort of premise can eliminate options that are actually quite valid solutions. Keep in mind that any mobile app will require multiple languages working in harmony - all while used in a commercially consistent and standards-based manner. That's the part that determines your technical scalability! Almost every programming language can achieve this functionality with an experienced developer on your team. The best advice I can give you, is to consult with at least two people on this, and three if your app is os-specific. The most important insight will come from a "full stack" developer. One who's got a variety of enterprise experience, and can code at all levels of the stack. This person needs to have experience in leading a team of other developers, which forces the strategy of which technologies to use and why onto their plates daily. Secondly, you'll want to consult with a "front end" developer, who can tell you what's possible using advanced OOP JavaScript techniques (like Google's angular.js), because in an absurdly fast change over the past 3 years, much of the formerly back-end work has made it's way to the front-end, and is driven by JavaScript, predominantly JSON data, and awesome API's. The game has changed and the front-enders are the poor souls dealing with this rapid shift daily. To do this, they're also fantastic JavaScript programmers, which is a language that runs on all mobile devices and all browsers, too. Love it or hate it JavaScript is the most commonly used language in the world. Finally, if your app is OS-specific, you'll want to consult with a developer who works predominantly with the OS your app is built for. This person lets you know what's possible from the device POV, should know what stacks and JavaScript approaches can and can't be done on that OS, and how to leverage the resources of the device for your app as well as extend it's functionality. BONUS - loop back to the full stack developer to double-check the claims of the front-ender and the mobile developers. Always double check with your most senior programmer ;) All of these consults together in addition to your own research and due diligence will get you comfortable and allow you to navigate on this rather daunting but deeply important journey. There aren't any turn-key options. Instead it's a series of inter-connected modules driven by different languages, and all working in tandem. Every solution will have bugs, and no one group of technologies can do everything without proper developers. If you'd like to go further down the rabbit hole, then we should definitely set-up some time to speak. Otherwise, I wish you great luck in research and encourage you to learn as much as you can! :) It's going to seem hard, and might give you a headache here or there, but learn everything you can about how different technologies "talk" to each other, and then you will be able to build a map for keeping your app and business scalable regardless of the changing tides of technology!MM
-
Do angel investors look for a certain number of active users when investing in an app startup that has recently launched, 5,000-10,000+?
First of all, there is no "one size fits all" attitude in angel investing. I will tell you that the *best* angels will make a snap decision by playing with the product and assessing founder/market fit. At the right valuation, the kinds of angels you really want backing you will invest purely based on a killer early product experience and conviction of founder/market fit. But if you have made your app available in the US app store already, you have made a critical tactical error if your app isn't already trending towards 100,000 installs within the first 30 days of availability. Apps should first launch in a non US, english-speaking store to do early product/market fit work. Your "day one" event in the US app store matters to seed investors and many angel investors. While there are exceptions (most often in SaaS or enterprise mobile models), there are only 4 times to raise funding from seed funds for a mobile start-up stage company: Pre-product: A deck, a market opportunity and a team. Pre-launch: Product fully built but holding launch for funding. This will usually involve a private beta of at least 1000 users or a soft launch in an international store. 30 - 90 days after US launch: Must be at or trending towards 100,000 installs with very strong month-over-month growth. If you miss those windows, the next time to raise is after you pass over 1,000,000 with strong retention and engagement that correlates to your business model and user personas. As a mobile-first entrepreneur and angel investor, I'm happy to talk to you about this in more detailTW
-
How can I sell my app idea, and do I need to get it patented?
This is a little hard to answer because it is so vague. It depends on the area, the market and the strength of innovation. I know that The App Guy has a terrific podcast at http://www.theappguy.co/ and is also trying to organize a community for App developers to sell their ideas. Let me know if I can be of further assistance to discuss patentability in terms of its value to getting a sale or license. What ever you do, don't spend money filing a full patent, just a provisional. Good luck.TH
-
If I'm looking to create a mobile app for my startup, should I first hire a designer or a developer?
Designer. Specifically a UX "designer" as you say, who doesn't just draw screens, and won't draw any for weeks or months. They will not just use their knowledge but will go out and talk to users, observe how they solve the same problem today, and help create the scope of work, and design the basic functionality. If you hire a developer first, they will build stuff that may or may not be of any value. If the company survives the first few rounds of building the wrong thing, you are still spending a hell of a lot in rebuilding, re-marketing, etc. etc.SH
-
Where is the best place to find an affordable mobile app developer?
You can hire app development freelancers from www.odesk.com and www.elance.com. I am an app developer myself, and I got profiles on both of these networks, a link is given below: https://www.odesk.com/users/~012d73aa92fad47188 Please feel free to get in touch to discuss ideas and clarify any confusions, I will be glad to help.NA
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.