- This topic is empty.
February 13, 2014 at 9:37 am #162768
I am building an app – I took my aweber layout and just want end user to fill in answers to pre-set questions and SAVE not submit – so when they open the app again that info is there.
Here is a snippet – can I change out ‘submit’ to ‘save’ or something?February 13, 2014 at 9:41 am #162769
You need to elaborate in more detail about this “app”. Take us through the process.February 13, 2014 at 9:46 am #162773
I have a html page linked from “Local Numbers” tab.
I basicly stole from my Aweber account the coding for the visual layout I like.
Insurance Company: …………………………….
Insurance Number: ………………………………
So the end user fills out this information (………. area). Now the problem with the aweber form is it has the ‘submit’ – I changed that out to say “Automotive Emergency App” hoping they don’t hit that to submit.
I would like that to say “save” so when they save the info they typed in it will be there the next time the open the app (and could edit of course)
yes?February 13, 2014 at 9:52 am #162779
so when they save the info they typed in it will be there the next time the open the app (and could edit of course)
How do you plan on identifying people? For example, if you wrote in information and I wrote information, how are you planning to distinguish me from you so the information that I entered shows up and not yours?
Does that make sense?February 13, 2014 at 9:57 am #162780
good question – it’s strictly information for the end user – I (as app owner) would never need or want the info – it doesn’t need to go into a database.
just save like ‘notes’ does – but in notes you can’t set the initial questions (Year/Make/Model) – I may be way out in left field here -there might be an easier way to do this. I’m just under the gun for this app update because of some big pending customers.. I don’t know how to use ‘pagegap’ which i guess let’s you write coding..February 13, 2014 at 10:08 am #162783
Are we talking about a web app?
I think you may want to take a look at PHP
setcookie(). This will allow you to store the information client side and choose when it expires. Strictly using
$_SESSIONwill not be appropriate here since the information will be lost when the user closes out their browser.February 13, 2014 at 10:11 am #162784
No, Sorry a Mobile App – you can search the store for ‘ThomsonMotors’ and download it (delete it when done) and you can have a visual – I don’t see where I can upload images here. I have a descent grip on HTML but PHP is out of my league..February 13, 2014 at 10:14 am #162785
I have no knowledge of developing for mobile apps. I don’t think I would be of any help.February 13, 2014 at 10:19 am #162789
ok – thanks for your patience – I appreciate your time..
WymettoFebruary 13, 2014 at 10:23 am #162791
I don’t either… but I’ll try. Mobile apps are typically written in Java, Objective C, or Visual Basic (I would assume this is what Win Phones use). Java is probably the most common because of the plethora of Android devices. This is presumably very easy… provided that you know one of these languages. If you want to build a web app… which I think would be a wise first step, @chrisburton is right, you can either do it client side or server side. If you do it server side, you have to use a database. There has to be somewhere to store that data. It’s not really about whether or not you would want it. Although, in my opinion, you’d probably be wise to have access to it. It’s easier to monetize your app in a creative way if you have access to user data. However, you’ll need to write a TOS agreement that discloses that.February 13, 2014 at 10:24 am #162792
I would jump on Reddit as this is a broad question we can’t help you with. Once you narrow down EXACTLY what you want to do, you can go to Stack Overflow and the good folks over there will help you. But be warned… you need to thoroughly research your problem before you post there.February 13, 2014 at 10:25 am #162794
Ok thanks guys – I will do that..February 13, 2014 at 12:23 pm #162810
It’s not necessarily that he needs a database, a cookie with a very long expiration date would suffice, it’s that it would be smarter in case the app expands where it would need that data (e.g. sharing mobile app data to web app).February 13, 2014 at 12:52 pm #162815
But aren’t all cookies client side? Admittedly, I don’t know much about any of this but the way I see it, there are two options. My vote would be to store that data in a database.February 13, 2014 at 1:46 pm #162825
- The forum ‘Other’ is closed to new topics and replies.