Loading...
Answers
MenuInitially is it a good idea to validate and launch a new concept via a desktop website or an app?
Currently working on a marketplace platform, not too sure if I will waste a lot of my time building a nice desktop platform over an app initially? Intentions are to build a native app following launch... But as a strategic move, I am thinking of building a desktop web-platform first. What advice and thoughts do you have on this please?
Answers
depends on the market, so it's IMPOSSIBLE to advise the correct approach/choice in this question. However, I'd lean towards a desktop/web app for anything that is trying to accomplish 'platform' level mechanics.... most noobs will use the term platform and app interchangeably but there is a huge difference: platforms are designed for OTHER COMPANIES/brands/power-users to BUILD FUNCTIONALITY on top of/extend the use for their specific purposes... TWITTER is a platform. "an app to buy/sell stuff in X new way or Y speciality or Z local/geographic market" is just an app that is trying to say it's cool by calling itself a platform because there's type major types of uses & 'transactions' involved.... a CHATROOM is an app... TWITTER is a platform. Hope that helps.
Generally speaking, I think building a web app for your marketplace concept first can be a great option to launch, then move on to develop a mobile app later on whenever it makes the most sense. Building a web app (vs. a native mobile app) will usually require less time, effort, and money, and if you build it right (responsive, etc.), it can potentially work pretty well across desktop, mobile, and tablet.
That said, there're many other considerations to think about. Here're a couple quick examples:
- target audience & their environment: if you're targeting millennials, mobile may be a lot more important than if your application is typically used by professionals during working hours (in which case web first is a definitive winner in my book).
- hardware needs: do you need to leverage camera / mic / video / sound / accelerometer / GPS a lot? if so, you may be better off building a native mobile app.
- validate: keep in mind you'll have to validate your concept at many different levels (problem, solution, marketing, channels, UVP, cost structure, price & revenue structure, etc). Building a web app can help with lots of this, but it wouldn't be the first move I'd recommend: if you haven't yet validated at least some of your assumptions around problem, solution, and customer segments, I'd suggest you consider validating your idea further before starting to build. And, as a side effect and while you do that, it may also become clearer whether a web app can work or if a mobile app is a must-have.
Just a quick couple thoughts to get you going. I work on this specific topic a lot with my prospects and clients (I build responsive web apps - including marketplaces -, but not mobile apps). I have advised different clients to go with mobile-first and web-first approaches on different occasions, and also advised a couple of them to go back and validate their ideas further before building anything. Let me know if you'd like to setup a call to go over some more specifics to your situation.
This decision depends primarily on your market and the specific needs.
Outside of knowing this key element, my initial reaction is that building a web application that is mobile friendly is a great option to start. If native apps (for various platforms) are desired to continue building your client base, then you can come in well informed from your base web application.
Related Questions
-
Does Wix.com support an API from Booking.com or other API for B2B Travel Agency?
Yes Wix supports a mulitude of APIs to used for various fetch calls for your web pages. If you already have to API's in mind you can venture off within you WIX code to integrate within your application's processes. There shouldn't be any complications getting this done. Please see the link below for more information https://www.wix.com/code/home/apiAB
-
What is the concept of strategic clarity in companies and what are its dimensions and strategies?
Strategic clarity is the ability to clearly define, quickly adapt, effectively communicate and properly implement the company's business strategies. It is the opposite of strategic ambiguity. Strategic clarity as a modern term or phrase most likely arises from a very real problem. That is, many businesses do not have a clear strategy or, the strategy they have is ambiguous. Frankly, I would bet that strategic clarity as a new term was probably coined by a business consultant or consultancy firm as a marketing ploy to differentiate themselves from their competitors. The term is catching on. Any business that does not have a clearly defined, adaptable, effectively communicated and properly implemented strategy is at best operating below its true potential, and at worst is in serious jepoardy. I offer free 30 minute consultations using the link below. Feel free to schedule a free call if you would like to discuss this further. https://clarity.fm/kevinmccarthy/FreeConsult All the best, Kevin McCarthy www.kevinmccarthy.comKM
-
Should I outsource the development of my app to a mobile development company? Which are recommended/reputable?
I recommend that you get technical cofounder as soon as possible. Using a contract developer to create a prototype is ok but keep in mind that startups need to iterate and be very flexible in the early stages of company/product development. A contract developer works best on a fixed spec and will be hard to adapt without a lot of extra costs and frustration on both sides. Go get a tech cofounder, somebody invested in your product and willing to be flexible and adapt as you discover what your product really is.DA
-
What learning path do I have to take to become a "full-stack" web developer?
If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.KD
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.