Member Avatar for 3xxx

hey, I am totoally window person

no experience with apple whatsoever except it is a multi-touch mouse that I know


say -- if I wanna to learn android, I start with

-----

I really wanna to learn write an apps for ipad

i.e. business application

I want it to be database driven too-- so if I have to do anything, I do it with query or database macro , stored procedure etc

someone please give me some GUIDELINE please, even basic stuff will help


I know my new company will got plenty of iphone, ipad, apple air mac book for me to play around

therefore, I really wanna to start to learn about apps programming

if it is FAKE apps, even better, I know there is wrapper around -- that company will wrap up a mini-web-site for you with a FEES

  • 2 Contributors
  • 1 Reply
  • 295 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by ChrisPadgham

Dani AI

Generated

Good place to start: treat iPad apps like any other platform project — get comfortable with the tools and pick a clear data strategy. For native iPad work the current stack is Swift for the language, SwiftUI for modern UIs, and Xcode as the IDE; these three are the fastest path to a polished iPad app and will pay off long term. (swift.org)

About “database-driven”: decide whether the authoritative data lives on the device or on a server. For local persistence Apple’s recommended option is Core Data (it’s object-oriented and uses an on-disk store under the hood), but its SQLite file format is private — Core Data is not the same as running raw SQL or stored procedures on the device. If you want a true SQL/stored-proc model, build a server-side database and expose a REST/GraphQL API the app talks to; if you want Apple-native sync, consider CloudKit. (developer.apple.com)

Practical options when you start coding: use Core Data + SwiftUI for most business CRUD apps, or use a mobile SQLite wrapper (for SQL-style queries) such as SQLite.swift or a mobile-first object DB like Realm if you prefer objects and easier sync. For quick proof-of-concept backend work, managed BaaS (Firebase, MongoDB Realm, etc.) can speed things up. Pick one stack and build a small end-to-end CRUD flow first (list, add, edit, delete, sync). (github.com)

Concrete next steps: install Xcode on the Mac you’ll use, follow a short Swift + SwiftUI tutorial, wire up simple persistence (Core Data or SQLite wrapper), test in the simulator and on device, and use TestFlight for beta distribution. To publish or use advanced entitlements you’ll need an Apple Developer account (current membership fee applies). Read Apple’s iPad design guidance so the UI fits iPad expectations. (developer.apple.com)

Thanks to for the question and to for the pointer toward structured learning — focus on small, complete apps (UI + local persistence + optional backend) and iterate.

Member Avatar for ChrisPadgham

in itunesu look for stanford university lectures by Paul Hegarty on iPhone development, this is a good start

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.